linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	rientjes@google.com, nishimura@mxp.nes.nec.co.jp
Subject: Re: [RFC][PATCH 1/2] memcg: oom kill handling improvement
Date: Fri, 26 Feb 2010 14:47:52 +0900	[thread overview]
Message-ID: <20100226144752.19734ff0.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20100226142339.7a67f1a8.kamezawa.hiroyu@jp.fujitsu.com>

On Fri, 26 Feb 2010 14:23:39 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 26 Feb 2010 13:15:52 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> 
> > On Wed, 24 Feb 2010 16:59:21 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > These are dump of patches just for showing concept, what I want to do.
> > > But not tested. please see if you have free time. (you can ignore ;)
> > > 
> > > Anyway, this will HUNK to the latest mmotm, Kirill's work is merged.
> > > 
> > > This is not related to David's work. I don't hesitate to rebase mine
> > > to the mmotm if his one is merged, it's easy.
> > > But I'm not sure his one goes to mm soon. 
> > > 
> > > 1st patch is for better handling oom-kill under memcg.
> > It's bigger than I expected, but it basically looks good to me.
> > 
> 
> BTW, do you think we need quick fix ? I can't think of a very easy/small fix
> which is very correct...
To be honest, yes.
IMHO, casing global oom because of memcg's oom is a very bad behavior
in the sence of resource isolation. But I agree it's hard to fix in simple way,
so leave it as it is for now..
hmm.. I must admit that I've not done enough oom test under very high pressure.


Thanks,
Daisuke Nishimura.

--
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>

  reply	other threads:[~2010-02-26  5:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  7:59 KAMEZAWA Hiroyuki
2010-02-24  8:01 ` [RFC][PATCH 2/2] memcg: oom kill nofify and disable oom kill for memcg KAMEZAWA Hiroyuki
2010-02-26  4:15 ` [RFC][PATCH 1/2] memcg: oom kill handling improvement Daisuke Nishimura
2010-02-26  4:50   ` KAMEZAWA Hiroyuki
2010-02-26  5:23   ` KAMEZAWA Hiroyuki
2010-02-26  5:47     ` Daisuke Nishimura [this message]
2010-02-26  7:17       ` KAMEZAWA Hiroyuki
2010-02-26 12:30         ` Daisuke Nishimura
2010-03-01  0:54           ` KAMEZAWA Hiroyuki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100226144752.19734ff0.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox