Lines Matching refs:that

10 It is important to note that there are two modes for a native allocator
21 When evaluating a native allocator, make sure that you benchmark both
25 Android supports a few non-standard functions and mallopt controls that
29 These are functions that are used to implement a memory leak detector
33 This function, when called, should pause all threads that are making a
51 These are mallopt options that Android requires for a native allocator
55 When set to zero, `mallopt(M_DECAY_TIME, 0)`, it is expected that an
65 The drawback to this option is that most allocators do not have a separate
67 allocation operation occurs. For server processes, this can mean that
73 made by default. The idea is that it allows application frees to run a
80 idea is that this can be called to purge memory that has not been
82 server application that does a lot of native allocations and the
83 application wants to purge that memory before waiting for the next connection.
86 These are the tests that should be run to verify an allocator is
101 that a native allocator will have its own set of tests that can be run.
104 The libmemunreachable tests verify that the iterator functions are working
117 In addition to the bionic tests, there is also a CTS test that is designed
118 to verify that the addresses returned by malloc are sufficiently randomized
135 been allocator bugs that cause memory failures when too much virtual
139 These are the microbenchmarks that are part of the bionic benchmarks suite of
153 and helps to get a number that can be compared to the new allocator.
189 useful to look at these kinds of benchmarks to make sure that there are
196 These are the benchmarks that examine how the allocator handles multiple
207 This benchmark is designed to verify that there is no performance issue
226 frees are not counted. Forty allocations is an arbitrary number that could
252 This benchmark is designed to verify that the allocator will be performant
270 This benchmark only verifies that mallinfo is still close to the performance
284 allocator, only that the performance be in the same order of magnitude.
319 on a thread as if it was rerunning the real trace. The only issue is that
349 a good idea to look over the data to verify that no strange spikes are
354 For any call that allocates a pointer, the time for the call and the time
365 rather than delete them. When that happens, it can lead to allocation
367 important to verify that when running this trace using the 32 bit replay
372 when running the memory traces acts as a proxy for this. An allocator that
376 up and down a bit, but stays mostly the same so an allocator that fragments
379 NOTE: When a native allocator calls mmap, it is expected that the allocator
390 of the maps that this allocator includes.
400 This is a benchmark that treats the trace data as if all allocations
401 occurred in a single thread. This is the scenario that could