From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
linux-kernel@vger.kernel.org, drepper@redhat.com,
riel@redhat.com, Martin Bligh <mbligh@mbligh.org>,
linux-mm@kvack.org
Subject: Re: OOM notifications
Date: Mon, 29 Oct 2007 02:46:40 +0530 [thread overview]
Message-ID: <4724FC38.30909@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071026140201.ae52757c.akpm@linux-foundation.org>
Andrew Morton wrote:
> It get more complicated with NUMA memory nodes and cgroup memory
> controllers.
>
At OLS this year, users wanted user space notification of OOM
for cgroup memory controller. When a group is about to OOM,
a notification can help an external application re-adjust
memory limits across the system.
Keeping some memory reserved for handling OOM, this scheme could
be extended to handle global OOM conditions as well.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-10-28 21:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 20:15 OOM notifications Marcelo Tosatti
2007-10-26 21:02 ` Andrew Morton
2007-10-26 21:05 ` Martin Bligh
2007-10-26 21:11 ` Andrew Morton
2007-10-26 21:35 ` Rik van Riel
2007-10-26 21:59 ` Martin Bligh
2007-10-26 22:30 ` Rik van Riel
2007-10-28 21:16 ` Balbir Singh [this message]
2007-10-30 14:57 ` Jan Kara
2007-10-30 15:23 ` Rik van Riel
2007-10-30 15:55 ` Jan Kara
2007-10-30 17:31 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 20:25 Marcelo Tosatti
2007-10-18 20:38 ` Rene Herman
2007-10-18 20:52 ` Rik van Riel
2007-10-18 21:06 ` Rene Herman
2007-10-18 21:18 ` Rik van Riel
2007-10-18 22:01 ` Rene Herman
2007-10-18 22:10 ` Ulrich Drepper
2007-10-19 5:15 ` Chris Friesen
2007-10-19 10:17 ` Pavel Machek
2007-10-19 15:18 ` Samuel Tardieu
2007-10-19 16:58 ` Chris Friesen
2007-10-18 22:16 ` Rene Herman
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=4724FC38.30909@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=mbligh@mbligh.org \
--cc=riel@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