Messages in this thread | | | From | Satoru Moriya <> | Subject | RE: [patch 3/7] mm: vmscan: clarify how swappiness, highest priority, memcg interact | Date | Tue, 18 Dec 2012 15:16:22 +0000 |
| |
On 12/17/2012 01:12 PM, Johannes Weiner wrote: > A swappiness of 0 has a slightly different meaning for global reclaim > (may swap if file cache really low) and memory cgroup reclaim (never > swap, ever). > > In addition, global reclaim at highest priority will scan all LRU > lists equal to their size and ignore other balancing heuristics. > UNLESS swappiness forbids swapping, then the lists are balanced based > on recent reclaim effectiveness. UNLESS file cache is running low, > then anonymous pages are force-scanned. > > This (total mess of a) behaviour is implicit and not obvious from the > way the code is organized. At least make it apparent in the code flow > and document the conditions. It will be it easier to come up with > sane semantics later. > > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Hmmm, my company's mail server is in trouble... The mail I sent yesterday has not been delivered yet.
Anyway, this is good for me. Thanks!
Reviewed-by: Satoru Moriya <satoru.moriya@hds.com>
| |