From: David Rientjes <rientjes@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"menage@google.com" <menage@google.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [discuss][memcg] oom-kill extension
Date: Tue, 28 Oct 2008 22:13:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0810282206260.10159@chino.kir.corp.google.com> (raw)
In-Reply-To: <20081029140012.fff30bce.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 29 Oct 2008, KAMEZAWA Hiroyuki wrote:
> > > Does anyone have plan to enhance oom-kill ?
> > >
> > > What I can think of now is
> > > - add an notifier to user-land.
> > > - receiver of notify should work in another cgroup.
> >
> > The discussion at the mini-summit was to notify a FIFO in the cgroup and any
> > application can listen in for events.
> >
> add FIFO rather than netlink or user mode helper ?
>
There was a patchset from February that added /dev/mem_notify to warn
userspace of low or out of memory conditions:
http://marc.info/?l=linux-kernel&m=120257050719077
http://marc.info/?l=linux-kernel&m=120257050719087
http://marc.info/?l=linux-kernel&m=120257062719234
http://marc.info/?l=linux-kernel&m=120257071219327
http://marc.info/?l=linux-kernel&m=120257071319334
http://marc.info/?l=linux-kernel&m=120257080919488
http://marc.info/?l=linux-kernel&m=120257081019497
http://marc.info/?l=linux-kernel&m=120257096219705
http://marc.info/?l=linux-kernel&m=120257096319717
Perhaps this idea can simply be reworked for the memory controller or
standalone cgroup?
--
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:[~2008-10-29 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 2:38 KAMEZAWA Hiroyuki
2008-10-29 4:08 ` Balbir Singh
2008-10-29 5:00 ` KAMEZAWA Hiroyuki
2008-10-29 5:13 ` David Rientjes [this message]
2008-10-29 5:28 ` KAMEZAWA Hiroyuki
2008-10-29 6:55 ` KOSAKI Motohiro
2008-10-29 5:35 ` Paul Menage
2008-10-29 5:45 ` KAMEZAWA Hiroyuki
2008-10-29 5:49 ` Paul Menage
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.1.10.0810282206260.10159@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=mtosatti@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