Lines Matching refs:of

8 to incur cost overheads of page stealing and possible swap io for
13 In the absence of non sleepable allocation requests, it seems detrimental
15 is, only when needed (aka zone free memory is 0), instead of making it
19 mapped pages from the direct mapped pool, instead of falling back on
22 OTOH, if there is a lot of free dma pages, it is preferable to satisfy
24 of incurring the overhead of regular zone balancing.
27 _total_ number of free pages fell below 1/64 th of total memory. With the
28 right ratio of dma and regular memory, it is quite possible that balancing
30 been running production machines of varying memory sizes, and seems to be
31 doing fine even with the presence of this problem. In 2.3, due to
34 In 2.3, zone balancing can be done in one of two ways: depending on the
35 zone size (and possibly of the size of lower class zones), we can decide
38 of lower class zones, the bad part is, we might do too frequent balancing
44 of a zone _and_ all its lower class zones falls below 1/64th of the
48 which have different numbers and types of zones. If we wanted to get
52 Note that if the size of the regular zone is huge compared to dma zone,
80 the number of pages falls below watermark[WMARK_MIN], the hysteric field
81 low_on_memory gets set. This stays set till the number of free pages becomes
85 That decision is not hysteresis based, and is done when the number of free
90 1. Dynamic experience should influence balancing: number of failed requests