Lines Matching refs:large
169 allocate very large blocks.
172 reallocate very large blocks.
468 allocate very large blocks. These will be returned to the
478 large blocks. This is currently only possible on Linux with
634 afterward allocate more large chunks) the value should be high
654 program undergoes phases where several large chunks are
658 controlling release of large blocks via trimming versus mapping
721 Using mmap segregates relatively large chunks of memory so that
747 only for relatively large requests.
769 3. If a program allocates many large regions, it is probably
951 /* resrve 64MB to insure large contiguous space */
1255 large (see M_TRIM_THRESHOLD).
1522 To help compensate for the large number of bins, a one-level index
2071 4. If large enough, the chunk bordering the end of memory
2075 chunk since it can be extended to be as large as necessary
2923 the malloc pool. You can call this after freeing large blocks of
2926 some allocation patterns, some large free blocks of memory will be
3221 * Use best fit for very large chunks to prevent some worst-cases.