Thread (23 messages) 23 messages, 8 authors, 2012-12-21

RE: [patch 3/7] mm: vmscan: clarify how swappiness, highest priority, memcg interact

From: Satoru Moriya <hidden>
Date: 2012-12-18 15:46:59
Also in: lkml

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>
Reviewed-by: Satoru Moriya <redacted>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help