[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090803212059.CC2C.A69D9226@jp.fujitsu.com>
Date: Mon, 3 Aug 2009 21:21:44 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: David Rientjes <rientjes@...gle.com>
Cc: kosaki.motohiro@...fujitsu.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Paul Menage <menage@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [patch -mm v2] mm: introduce oom_adj_child
> On Sat, 1 Aug 2009, KAMEZAWA Hiroyuki wrote:
>
> > Summarizing I think now .....
> > - rename mm->oom_adj as mm->effective_oom_adj
> > - re-add per-thread oom_adj
> > - update mm->effective_oom_adj based on per-thread oom_adj
> > - if necessary, plz add read-only /proc/pid/effective_oom_adj file.
> > or show 2 values in /proc/pid/oom_adj
> > - rewrite documentation about oom_score.
> > " it's calclulated from _process's_ memory usage and oom_adj of
> > all threads which shares a memor context".
> > This behavior is not changed from old implemtation, anyway.
> > - If necessary, rewrite oom_kill itself to scan only thread group
> > leader. It's a way to go regardless of vfork problem.
> >
>
> Ok, so you've abandoned the signal_struct proposal and now want to add it
> back to task_struct with an effective member in mm_struct by changing the
> documentation. Hmm.
Oops, please see From line. The page was made from me ;)
--
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