Lines Matching refs:of

6   o Slab allocation of small objects of unknown type (kmalloc)
7   o Slab allocation of small objects of known type
12 This document describes what each of the tracepoints is and why they
15 1. Slab allocation of small objects of unknown type
23 internal fragmented as a result of the allocation pattern. By correlating
28 2. Slab allocation of small objects of known type
36 of writing, no information is available on what slab is being allocated from,
47 a simple indicator of page allocator activity. Pages may be allocated from
52 amounts of activity imply high activity on the zone->lock. Taking this lock
57 is triggered. Significant amounts of activity here could indicate that the
62 freed in batch with a page list. Significant amounts of activity here could
71 In front of the page allocator is a per-cpu page allocator. It exists only
73 amount of writing on struct page.
75 When a per-CPU list is empty or pages of the wrong type are allocated,
80 When the per-CPU list is too full, a number of pages are freed, each one
83 The individual nature of the events is so that pages can be tracked
84 between allocation and freeing. A number of drain or refill pages that occur
85 consecutively imply the zone->lock being taken once. Large amounts of per-CPU
88 lists should be a larger size. Finally, large amounts of refills on one CPU
89 and drains on another could be a factor in causing large amounts of cache
98 successful or not. For some types of hardware, this is important although
100 to be able to resize the pool over the lifetime of the system, this value
103 Large numbers of this event implies that memory is fragmenting and
105 means of reducing the occurrence of this event is to increase the size of
106 min_free_kbytes in increments of 3*pageblock_size*nr_online_nodes where
107 pageblock_size is usually the size of the default hugepage size.