linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Michal Hocko <mhocko@suse.cz>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-mm@kvack.org
Subject: Re: [patch v2] oom: thaw threads if oom killed thread is frozen before deferring
Date: Tue, 11 Oct 2011 16:46:34 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1110111645090.5236@chino.kir.corp.google.com> (raw)
In-Reply-To: <20111011233914.GC6281@google.com>

On Tue, 11 Oct 2011, Tejun Heo wrote:

> > If that's possible, then we can just add Tejun to add a follow-up patch to 
> > remove the thaw directly in the oom killer.  I'm thinking that won't be 
> > possible for 3.2, though, so I don't know why we'd remove 
> > oom-thaw-threads-if-oom-killed-thread-is-frozen-before-deferring.patch 
> > from -mm?
> 
> Yeah, it's a bit unclear.  All (or at least most) patches which were
> necessary for this patch was queued in Rafael's tree before korg went
> belly up and then we both lost track of the tree and I need to
> regenerate the tree and ask Rafael to pull again.

Eek, what a pain.

> I think the merge
> window is already too close, so please go ahead with the acked fix.
> Let's clean it up during the next devel cycle.
> 

Ok, sounds good.  When frozen oom killed threads can always move down the 
exit path, then we can just remember to remove the thaw_process() from the 
oom killer.

Thanks.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-10-11 23:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08  2:56 [patch resend] " David Rientjes
2011-10-08  2:59 ` [patch v2] " David Rientjes
2011-10-08  7:23   ` KOSAKI Motohiro
2011-10-11  6:33     ` Michal Hocko
2011-10-11 14:50       ` KOSAKI Motohiro
2011-10-11 15:14         ` Michal Hocko
2011-10-11 15:57           ` KOSAKI Motohiro
2011-10-11 19:07             ` Michal Hocko
2011-10-11 23:36       ` David Rientjes
2011-10-11 23:39         ` Tejun Heo
2011-10-11 23:46           ` David Rientjes [this message]
2011-10-12  6:50         ` Michal Hocko
2011-10-12  6:58           ` Michal Hocko
2011-10-11 19:16 ` [patch resend] " Oleg Nesterov
2011-10-11 23:30   ` David Rientjes
2011-10-11 23:41     ` Andrew Morton
2011-10-12 14:40     ` Oleg Nesterov

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.1110111645090.5236@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=htejun@gmail.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=oleg@redhat.com \
    --cc=rjw@sisk.pl \
    /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