[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110930074641.GK10425@mtj.dyndns.org>
Date: Fri, 30 Sep 2011 00:46:41 -0700
From: Tejun Heo <htejun@...il.com>
To: Michal Hocko <mhocko@...e.cz>
Cc: Oleg Nesterov <oleg@...hat.com>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Konstantin Khlebnikov <khlebnikov@...nvz.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [patch] oom: thaw threads if oom killed thread is frozen before
deferring
Hello,
On Fri, Sep 30, 2011 at 09:41:25AM +0200, Michal Hocko wrote:
> > With pending freezer changes, allowing TIF_MEMDIE tasks to exit
> > freezer by modifying freezing() shouldn't be difficult, which should
> > be race-free and much simpler than diddling with thaw_task().
>
> Will the rework help with the initial problem of unkillable OOM selected
> frozen tasks or it will just help with other races that might be present
> with the patch? In other words will this work deprecate the 2 patches
> sent earlier in this thread?
I think it shouldn't be difficult to allow OOM-killing frozen tasks.
That should be good enough, right?
> > How urgent is this? Can we wait for the next merge window?
>
> Yes, I think we can wait some more.
I'm still processing rather large backlog. I'll ping you back once I
sort out the pending freezer changes.
Thanks.
--
tejun
--
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