Lines Matching refs:in

11 to run in on Android. The first is the normal allocator, the second is
18 The `BoardConfig.mk` file is usually found in the directory
19 `device/<DEVICE_NAME>/` or in a sub directory.
44 This function enumerates all of the allocations currently live in the
48 tests for this funcion in `bionic/tests/malloc_itearte_test.cpp`.
57 kernel on free calls. This is important in Android to avoid consuming extra
70 force a purge in this case.
130 allocator on Android. One is allocation speed in various different scenarios,
133 The last is virtual address space consumed in 32 bit applications. There is
134 a limited amount of address space available in 32 bit apps, and there have
163 to fluctuate in indeterminate ways.
175 single allocation, touching every page in the allocation to make it resident
188 The last value in the output is the size of the allocation in bytes. It is
200 in one loop, and then frees all of the allocations at the end of the loop.
221 do in each loop.
223 The other variation of this benchmark is to always do forty allocations in
227 be modified in the future. It was chosen because a version of the native
240 For these benchmarks, the last parameter in the output is the size of the
241 allocation in bytes.
243 As with the other microbenchmarks, an allocator with numbers in the same
253 in a real world allocation scenario. SQL operations were chosen as a
278 Calls to mallinfo are used in ART so a new allocator is required to be
284 allocator, only that the performance be in the same order of magnitude.
321 in all threads since it collapses all of the allocation operations to occur
344 checked in as zip files.
355 it takes to make the pointer completely resident in memory is included.
359 current allocator. But, they should be in the same range as the current
373 is fragmenting badly will show an increase in RSS. The best trace for
377 badly would likely show an abnormal increase in RSS on this trace.
392 In addition, in order for the frameworks code to keep track of the memory
401 occurred in a single thread. This is the scenario that could
402 happen if all of the allocations are spaced out in time so no thread
411 traces and display data. It takes many minutes to complete these runs in