No, by lazy in this context I meant that freed memory (pages) are not immediately moved to the free list. This even extends to task termination. If memory pressure ramps up sufficiently, kswapd will get kicked to balance out the trees. Could take a while - like forever.
In addition to what Rob mentioned, there is de-dup and compressed swap cache out in the wild already. How does the mug end user figure out what's what ?. Shane ... On Thu, Apr 12th, 2012 at 5:56 PM, Rob van der Heij <[email protected]> wrote: > ... (assume Shane hints at that with "lazy"). ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
