linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Badari <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: Wed, 31 Oct 2007 00:31:19 -0400	[thread overview]
Message-ID: <20071031003119.05dc064e@bree.surriel.com> (raw)
In-Reply-To: <472801DC.6050802@us.ibm.com>

On Tue, 30 Oct 2007 21:17:32 -0700
Badari <pbadari@us.ibm.com> wrote:

> Rik van Riel wrote:
> > 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".
> >
> >   
> I think having this kind of OOM notification is a decent start. But
> any applications that
> wants to know notifications, would be more interested if kernel is 
> swapping out any of
> its data, 

Well, if the scheme is implemented "right", then what you
describe will never happen because programs will have freed
their excess memory already before any swapping happens.

Tweaking the wakeup selection by NUMA node probably makes
sense as a future enhancement, though.

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

--
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>

  reply	other threads:[~2007-10-31  4:31 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
2007-10-31  4:17     ` Badari
2007-10-31  4:31       ` Rik van Riel [this message]
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=20071031003119.05dc064e@bree.surriel.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).