[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090803170217.e98b2e46.kamezawa.hiroyu@jp.fujitsu.com>
Date: Mon, 3 Aug 2009 17:02:17 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Paul Menage <menage@...gle.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch -mm v2] mm: introduce oom_adj_child
On Mon, 3 Aug 2009 00:59:18 -0700 (PDT)
David Rientjes <rientjes@...gle.com> wrote:
> > > - /proc/pid/oom_score is inconsistent when the thread that set the
> > > effective per-mm oom_adj exits and it is now obsolete since you have
> > > no way to determine what the next effective oom_adj value shall be.
> > >
> > plz re-caluculate it. it's not a big job if done in lazy way.
> >
>
> You can't recalculate it if all the remaining threads have a different
> oom_adj value than the effective oom_adj value from the thread that is now
> exited.
Then, crazy google apps pass different oom_adjs to each thread ?
And, threads other than thread-group-leader modifies its oom_adj.
Hmm, interesting.
Thanks,
-Kame
--
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