linux-kernel - Re: [PATCH] splitlru: memcg swapbacked pages active

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0806291302160.787@blonde.site>
Date:	Sun, 29 Jun 2008 13:20:42 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Rik van Riel <riel@...hat.com>,
	Lee Schermerhorn <lee.schermerhorn@...com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Balbir Singh <balbir@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] splitlru: memcg swapbacked pages active

On Sun, 29 Jun 2008, KOSAKI Motohiro wrote:
> > add_to_page_cache_lru puts PageSwapBacked pages on the active_anon lru,
> > so shouldn't mem_cgroup_charge_common mirror that by setting FLAG_ACTIVE?
> > 
> > Signed-off-by: Hugh Dickins <hugh@...itas.com>
> 
> I don't think so.
> 
> in global lru, active vs inactive anon ratio is controlled by 
> inactive_anon_is_low().
> but memcg doesn't have any sililar things.
> 
> thus, this patch increase active anon. and too many active page cause
> decrease reclaim throuput.
> 
> yes, We should implement SEQ replacement reclaim (like global reclaim)
> for memcg.
> I'm working on this.

Hmm.  Thanks for looking into it (and the others).  This is something
I noticed as a discrepancy in the source, rather than something from
which I observed any OOMs.  So if you're already working on bringing
the global and memcg approaches into line, I defer to your judgement.

But it seems to me worrying and fragile while they diverge in this way.
If the global has anon, active anon, file, active file and unevictable
lrus for the page; and the memcg has anon, active anon, file, active file
and unevictable lrus for the page cgroup; but different choices are made
which to put on where, then we're heading for confusion and trouble.

And when called, __mem_cgroup_move_lists tries to keep the activ-ity of
the memcg lrus in step with the activ-ity of the global lrus, doesn't
it?  So it's beyond my comprehension to start them off out of step.

Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/