From: Rik van Riel <riel@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
linux-mm <linux-mm@kvack.org>,
drepper@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
mbligh@mbligh.org, balbir@linux.vnet.ibm.com
Subject: Re: [RFC] oom notifications via /dev/oom_notify
Date: Tue, 30 Oct 2007 17:12:09 -0400 [thread overview]
Message-ID: <20071030171209.0caae1d5@cuia.boston.redhat.com> (raw)
In-Reply-To: <1193781568.8904.33.camel@dyn9047017100.beaverton.ibm.com>
On Tue, 30 Oct 2007 13:59:28 -0800
Badari Pulavarty <pbadari@us.ibm.com> wrote:
> Interesting.. Our database folks wanted some kind of notification when
> there is memory pressure and we are about to kill the biggest consumer
> (in most cases, the most useful application :(). What actually they
> want is a way to get notified, so that they can shrink their memory
> footprint in response. Just notifying before OOM may not help, since
> they don't have time to react. How does this notification help ? Are
> they supposed to monitor swapping activity and decide ?
Marcelo's code monitors swapping activity and will let userspace
programs (that poll/select the device node) know when they should
shrink their memory footprint.
This is not "OOM" in the sense of "no more memory or swap", but
in the sense of "we're low on memory - if you don't free something
we'll slow you down by swapping stuff".
--
All Rights Reversed
--
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:[~2007-10-30 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 19:18 [RFC] oom notifications via /dev/oom_notify Marcelo Tosatti
2007-10-30 20:57 ` Balbir Singh
2007-10-30 22:16 ` Marcelo Tosatti
2007-10-30 21:00 ` Rik van Riel
2007-10-30 21:07 ` Marcelo Tosatti
2007-10-30 21:19 ` Rik van Riel
2007-10-30 22:26 ` Marcelo Tosatti
2007-10-31 17:20 ` Dave Jones
2007-11-01 23:58 ` Marcelo Tosatti
2007-10-30 21:59 ` Badari Pulavarty
2007-10-30 21:12 ` Rik van Riel [this message]
2007-10-31 4:17 ` Badari
2007-10-31 4:31 ` Rik van Riel
2007-10-31 17:01 ` Badari Pulavarty
2007-10-31 16:15 ` Rik van Riel
2007-10-31 5:38 ` Balbir Singh
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=20071030171209.0caae1d5@cuia.boston.redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=drepper@redhat.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@kvack.org \
--cc=mbligh@mbligh.org \
--cc=pbadari@us.ibm.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;
as well as URLs for NNTP newsgroup(s).