From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>
Cc: linux-mm@kvack.org, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: oom killer rewrite
Date: Tue, 25 May 2010 17:02:53 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1005251700560.15789@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005250246170.8045@chino.kir.corp.google.com>
On Tue, 25 May 2010, David Rientjes wrote:
> > > oom-avoid-race-for-oom-killed-tasks-detaching-mm-prior-to-exit.patch
> > no objection. but afaik Oleg already pointed out "if (!p->mm)" is bad.
> > So, Don't we need push his patch instead?
> >
>
> I think it all depends on the order in which this work is merged.
>
I just noticed that Oleg's patches were dropped as well from -mm so I'll
merge them into my set and repost them as well.
--
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-05-26 0:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 22:14 David Rientjes
2010-05-20 0:27 ` KAMEZAWA Hiroyuki
2010-05-25 9:42 ` David Rientjes
2010-05-26 0:17 ` KAMEZAWA Hiroyuki
2010-05-26 1:40 ` David Rientjes
2010-05-26 2:00 ` KAMEZAWA Hiroyuki
2010-05-26 3:26 ` David Rientjes
2010-05-24 1:09 ` KOSAKI Motohiro
2010-05-24 7:07 ` Nick Piggin
2010-05-25 9:46 ` David Rientjes
2010-05-25 10:05 ` Nick Piggin
2010-05-25 10:23 ` David Rientjes
2010-05-25 10:31 ` Nick Piggin
2010-05-25 9:55 ` David Rientjes
2010-05-26 0:02 ` David Rientjes [this message]
2010-05-28 5:27 ` KOSAKI Motohiro
2010-05-28 5:25 ` KOSAKI Motohiro
2010-06-01 7:30 ` David Rientjes
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=alpine.DEB.2.00.1005251700560.15789@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.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