Proceedings of the 17th ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications - OOPSLA ' 2002
DOI: 10.1145/582419.582421
|View full text |Cite
|
Sign up to set email alerts
|

Reconsidering custom memory allocation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
97
1
1

Year Published

2005
2005
2013
2013

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 104 publications
(99 citation statements)
references
References 22 publications
0
97
1
1
Order By: Relevance
“…To handle synchronization as described in Section 3.3 and address space layout differences as described in Section 3.7, someone has to implement the appropriate interposers. Besides highly application-dependent use of pointer values to index data structures, many real-world applications use custom synchronization mechanisms [42] as well as custom memory allocators [7] besides the standard glibc and pthread primitives (despite the cited literature demonstrating how bad that customization practice is). In all these cases, the application developers themselves are responsible (1) for ensuring that interposers can handle all cases correctly, and (2) for providing the interposers.…”
Section: Experimental Evaluationmentioning
confidence: 99%
“…To handle synchronization as described in Section 3.3 and address space layout differences as described in Section 3.7, someone has to implement the appropriate interposers. Besides highly application-dependent use of pointer values to index data structures, many real-world applications use custom synchronization mechanisms [42] as well as custom memory allocators [7] besides the standard glibc and pthread primitives (despite the cited literature demonstrating how bad that customization practice is). In all these cases, the application developers themselves are responsible (1) for ensuring that interposers can handle all cases correctly, and (2) for providing the interposers.…”
Section: Experimental Evaluationmentioning
confidence: 99%
“…However, Berger et al suggest in [1] that region based approaches suffer from increased memory consumption due to retarded deallocation if the programmer is unwilling to adjust his or her programming style to suit the region approach and they propose a more generalised version of regions.…”
Section: Appaux(ythis):voidmentioning
confidence: 99%
“…We designed a custom memory manager for the single threaded version of TRIP, called rlalloc in this paper, in order to reduce the overhead in the allocation of elements of lists. The design of an efficient custom memory manager is an hard task as shown in the Berger's review [13]. Our memory manager splits a large memory chunk requested from the operating system in individual blocks of the size of the element of the recursive list representation.…”
Section: Memory Management For a Recursive List Representationmentioning
confidence: 99%