mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
	linux-kernel@vger.kernel.org, drepper@redhat.com
Subject: Re: OOM notifications
Date: Tue, 30 Oct 2007 11:23:46 -0400	[thread overview]
Message-ID: <20071030112346.4b48bfe5@cuia.boston.redhat.com> (raw)
In-Reply-To: <20071030145720.GB27039@atrey.karlin.mff.cuni.cz>

On Tue, 30 Oct 2007 15:57:20 +0100
Jan Kara <jack@suse.cz> wrote:

>   Hello,
> 
> > AIX contains the SIGDANGER signal to notify applications to free up some
> > unused cached memory:
> > 
> > http://www.ussg.iu.edu/hypermail/linux/kernel/0007.0/0901.html
> > 
> > There have been a few discussions on implementing such an idea on Linux,
> > but nothing concrete has been achieved.
> > 
> > On the kernel side Rik suggested two notification points: "about to
> > swap" (for desktop scenarios) and "about to OOM" (for embedded-like
> > scenarios).
> > 
> > With that assumption in mind it would be necessary to either have two
> > special devices for notification, or somehow indicate both events
> > through the same file descriptor.
>   Actually, wouldn't a generic netlink interface be more elegant? Then
> we could connect it with DBUS and it would be much easier for
> applications (Desktop) to handle such events.
>   I agree that near-to-oom conditions are quite volatile and maybe we
> want a technically simple (and thus more reliable) mechanism for the
> notification but I anyway wanted to point to this possibility.

There's nothing wrong with being able to get this info via DBUS,
but we cannot expect every database and JVM out there (big targets
for the "reduce your memory footprint" thing on servers) to grow
a DBUS interface.

-- 
All Rights Reversed

  reply	other threads:[~2007-10-30 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 20:15 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
2007-10-30 14:57 ` Jan Kara
2007-10-30 15:23   ` Rik van Riel [this message]
2007-10-30 15:55     ` Jan Kara
2007-10-30 17:31       ` Rik van Riel
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=20071030112346.4b48bfe5@cuia.boston.redhat.com \
    --to=riel@redhat.com \
    --cc=drepper@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@kvack.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

all inboxes | Powered by JetHome®