From: Evgeniy Polyakov <zbr@ioremap.net>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Nikanth Karthikesan <knikanth@suse.de>,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Arve Hj?nnev?g <arve@android.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Snook <csnook@redhat.com>,
Torvalds <torvalds@linux-foundation.org>,
Paul Menage <menage@google.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC] [PATCH] Cgroup based OOM killer controller
Date: Wed, 28 Jan 2009 00:54:07 +0300 [thread overview]
Message-ID: <20090127215407.GB12431@ioremap.net> (raw)
In-Reply-To: <20090127154053.GQ504@balbir.in.ibm.com>
On Tue, Jan 27, 2009 at 09:10:53PM +0530, Balbir Singh (balbir@linux.vnet.ibm.com) wrote:
> > Having some special application which will monitor /dev/mem_notify and
> > kill processes based on its own hueristics is a good idea, but when it
> > fails to do its work (or does not exist) system has to have ability to
> > make a progress and invoke a main oom-killer.
>
> The last part is what we've discussed in the mini-summit. There should
> be OOM kill notification to user space and if that fails let the kernel
> invoke the OOM killer. The exact interface for notification is not
> interesting, one could use netlink if that works well.
Yes, that's exactly what I would like to see.
Btw, netlink will not be a good idea, since it requires additional (and
quite big) allocation. I believe just reading the char device (or maybe
having a syscall) is enough, but its up to the implementation.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2009-01-27 21:54 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 11:08 [RFC] [PATCH] Cgroup based OOM killer controller Nikanth Karthikesan
2009-01-21 13:17 ` Evgeniy Polyakov
2009-01-21 15:24 ` Nikanth Karthikesan
2009-01-21 20:49 ` David Rientjes
2009-01-22 2:53 ` KAMEZAWA Hiroyuki
2009-01-22 5:12 ` Nikanth Karthikesan
2009-01-22 5:12 ` Nikanth Karthikesan
2009-01-22 8:43 ` David Rientjes
2009-01-22 9:23 ` Nikanth Karthikesan
2009-01-22 9:39 ` David Rientjes
2009-01-22 10:10 ` Nikanth Karthikesan
2009-01-22 10:18 ` David Rientjes
2009-01-22 9:50 ` Evgeniy Polyakov
2009-01-22 10:00 ` David Rientjes
2009-01-22 10:14 ` Evgeniy Polyakov
2009-01-22 10:27 ` David Rientjes
2009-01-22 13:21 ` Evgeniy Polyakov
2009-01-22 20:28 ` David Rientjes
2009-01-22 21:06 ` Evgeniy Polyakov
2009-01-22 21:35 ` David Rientjes
2009-01-22 22:04 ` Evgeniy Polyakov
2009-01-22 22:28 ` David Rientjes
2009-01-22 22:53 ` Evgeniy Polyakov
2009-01-22 23:25 ` Evgeniy Polyakov
2009-01-27 23:55 ` Paul Menage
2009-01-23 9:45 ` Nikanth Karthikesan
2009-01-23 10:33 ` David Rientjes
2009-01-23 14:56 ` Nikanth Karthikesan
2009-01-23 20:44 ` David Rientjes
2009-01-27 10:20 ` Nikanth Karthikesan
2009-01-27 10:53 ` David Rientjes
2009-01-27 11:08 ` Nikanth Karthikesan
2009-01-27 11:21 ` David Rientjes
2009-01-27 11:37 ` Nikanth Karthikesan
2009-01-27 20:29 ` David Rientjes
2009-01-28 1:00 ` Paul Menage
2009-01-29 15:48 ` Nikanth Karthikesan
2009-01-22 3:28 ` KAMEZAWA Hiroyuki
2009-01-22 5:13 ` Nikanth Karthikesan
2009-01-22 5:27 ` KAMEZAWA Hiroyuki
2009-01-22 6:11 ` Nikanth Karthikesan
2009-01-22 5:39 ` Arve Hjønnevåg
2009-01-22 6:12 ` Nikanth Karthikesan
2009-01-22 6:29 ` Arve Hjønnevåg
2009-01-22 6:42 ` Nikanth Karthikesan
2009-01-26 19:54 ` Balbir Singh
2009-01-26 19:56 ` Alan Cox
2009-01-27 7:02 ` KOSAKI Motohiro
2009-01-27 7:26 ` Balbir Singh
2009-01-27 7:39 ` David Rientjes
2009-01-27 7:44 ` KOSAKI Motohiro
2009-01-27 7:51 ` David Rientjes
2009-01-27 9:31 ` Evgeniy Polyakov
2009-01-27 9:37 ` David Rientjes
2009-01-27 13:40 ` Evgeniy Polyakov
2009-01-27 20:37 ` David Rientjes
2009-01-27 21:51 ` Evgeniy Polyakov
2009-01-27 10:40 ` KOSAKI Motohiro
2009-01-27 13:45 ` Evgeniy Polyakov
2009-01-27 15:40 ` Balbir Singh
2009-01-27 21:54 ` Evgeniy Polyakov [this message]
2009-01-27 20:41 ` David Rientjes
2009-01-27 21:55 ` Evgeniy Polyakov
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=20090127215407.GB12431@ioremap.net \
--to=zbr@ioremap.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arve@android.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=csnook@redhat.com \
--cc=knikanth@suse.de \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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