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>,
kirill@shutemov.name,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [RFC][PATCH 1/3] memcg: wake up filter in oom waitqueue
Date: Fri, 12 Mar 2010 11:54:29 +0900 [thread overview]
Message-ID: <20100312115429.b1b0d994.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20100312113838.d6072ae4.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 12 Mar 2010 11:38:38 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Fri, 12 Mar 2010 11:30:28 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
>
> > On Thu, 11 Mar 2010 16:55:59 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > > + /* check hierarchy */
> > > + if (!css_is_ancestor(&oom_wait_info->mem->css, &wake_mem->css) &&
> > > + !css_is_ancestor(&wake_mem->css, &oom_wait_info->mem->css))
> > > + return 0;
> > > +
> > I think these conditions are wrong.
> > This can wake up tasks in oom_wait_info->mem when:
> >
> > 00/ <- wake_mem: use_hierarchy == false
> > aa/ <- oom_wait_info->mem: use_hierarchy == true;
> >
> Hmm. I think this line bails out above case.
>
> > + if (!oom_wait_info->mem->use_hierarchy || !wake_mem->use_hierarchy)
> > + return 0;
>
> No ?
>
Oops! you're right. I misunderstood the code.
Then, this patch looks good to me.
Reviewed-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
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>
next prev parent reply other threads:[~2010-03-12 3:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 7:53 [RFC][PATCH 0/3] memcg: oom notifier at el. (v3) KAMEZAWA Hiroyuki
2010-03-11 7:55 ` [RFC][PATCH 1/3] memcg: wake up filter in oom waitqueue KAMEZAWA Hiroyuki
2010-03-12 2:30 ` Daisuke Nishimura
2010-03-12 2:38 ` KAMEZAWA Hiroyuki
2010-03-12 2:54 ` Daisuke Nishimura [this message]
2010-03-12 3:03 ` KAMEZAWA Hiroyuki
2010-03-11 7:57 ` [RFC][PATCH 2/3] memcg: oom notifier KAMEZAWA Hiroyuki
2010-03-11 14:47 ` Kirill A. Shutemov
2010-03-11 23:54 ` KAMEZAWA Hiroyuki
2010-03-11 7:58 ` [RFC][PATCH 3/3] memcg: oom kill disable and stop and go hooks 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=20100312115429.b1b0d994.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=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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