Lines Matching full:zone
21 is, only when needed (aka zone free memory is 0), instead of making it
30 of incurring the overhead of regular zone balancing.
35 would not be done even when the dma zone was completely empty. 2.2 has
40 In 2.3, zone balancing can be done in one of two ways: depending on the
41 zone size (and possibly of the size of lower class zones), we can decide
43 zone. The good part is, while balancing, we do not need to look at sizes
50 of a zone _and_ all its lower class zones falls below 1/64th of the
51 total memory in the zone and its lower class zones. This fixes the 2.2
58 Note that if the size of the regular zone is huge compared to dma zone,
60 deciding whether to balance the regular zone. The first solution
65 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
68 fall back into regular zone. This also makes sure that HIGHMEM pages
76 need to balance the highmem zone, since intr context does not request
77 highmem pages. kswapd looks at the zone_wake_kswapd field in the zone
78 structure to decide whether a zone needs balancing.
81 alleviate memory pressure on any zone in the page's node that has fallen below
85 are per-zone fields, used to determine when a zone needs to be balanced. When
89 try to free some pages in the zone (providing GFP_WAIT is set in the request).
90 Orthogonal to this, is the decision to poke kswapd to free some zone pages.
98 for a zone can be tracked and fed into the balancing scheme (jalvo@mbay.net)