[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0911031220170.25890@chino.kir.corp.google.com>
Date: Tue, 3 Nov 2009 12:24:01 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
minchan.kim@...il.com, vedran.furac@...il.com,
Hugh Dickins <hugh.dickins@...cali.co.uk>
Subject: Re: [RFC][-mm][PATCH 3/6] oom-killer: count lowmem rss
On Mon, 2 Nov 2009, KAMEZAWA Hiroyuki wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
>
> Count lowmem rss per mm_struct. Lowmem here means...
>
> for NUMA, pages in a zone < policy_zone.
> for HIGHMEM x86, pages in NORMAL zone.
> for others, all pages are lowmem.
>
> Now, lower_zone_protection[] works very well for protecting lowmem but
> possiblity of lowmem-oom is not 0 even if under good protection in the kernel.
> (As fact, it's can be configured by sysctl. When we keep it high, there
> will be tons of not-for-use memory but system will be protected against
> rare event of lowmem-oom.)
Right, lowmem isn't addressed currently by the oom killer. Adding this
constraint will probably make the heuristics much harder to write and
understand. It's not always clear that we want to kill a task using
lowmem just because another task needs some, for instance. Do you think
we'll need a way to defer killing any task is no task is heuristically
found to be hogging lowmem?
--
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/
Powered by blists - more mailing lists