From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: mhocko@suse.cz
Cc: rientjes@google.com, akpm@linux-foundation.org, oleg@redhat.com,
kamezawa.hiroyu@jp.fujitsu.com, rjw@sisk.pl, linux-mm@kvack.org,
htejun@gmail.com
Subject: Re: [patch v2] oom: thaw threads if oom killed thread is frozen before deferring
Date: Tue, 11 Oct 2011 11:57:35 -0400 [thread overview]
Message-ID: <4E94676F.2030302@jp.fujitsu.com> (raw)
In-Reply-To: <20111011151412.GF23284@tiehlicka.suse.cz>
> To sum up. There are 3 patches flying around at the moment.
> http://permalink.gmane.org/gmane.linux.kernel.mm/68576
> http://permalink.gmane.org/gmane.linux.kernel.mm/68577
> http://permalink.gmane.org/gmane.linux.kernel.mm/68583
>
> They are approaching the problem by thawing oom selected frozen task.
>
> Tejun mentioned his work (sorry I do not have a link to patches) that
> should enable direct killing frozen tasks. This would mean that we do
> not need any special handling from the OOM code paths AFAIU. This would
> be much better of course and I guess we can wait for them for 3.2.
>
> Does this make sense?
I don't find any bad in the idea. So, I have two questions.
o Who are writing such patch now?
o Should we drop current drientjes patch?
--
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>
next prev parent reply other threads:[~2011-10-11 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 2:56 [patch resend] oom: thaw threads if oom killed thread is frozen before deferring 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 [this message]
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
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=4E94676F.2030302@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=oleg@redhat.com \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.