Lines Matching refs:memory

17 is, only when needed (aka zone free memory is 0), instead of making it
25 regular memory requests by allocating one from the dma pool, instead
28 In 2.2, memory balancing/page reclamation would kick off only when the
29 _total_ number of free pages fell below 1/64 th of total memory. With the
30 right ratio of dma and regular memory, it is quite possible that balancing
32 been running production machines of varying memory sizes, and seems to be
45 Another possible solution is that we balance only when the free memory
47 total memory in the zone and its lower class zones. This fixes the 2.2
60 problems: first, kswapd is woken up as in 2.2 on low memory conditions
76 Page stealing from process memory and shm is done if stealing the page would
77 alleviate memory pressure on any zone in the page's node that has fallen below