From: Rene Herman <rene.herman@keyaccess.nl>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: linux-kernel@vger.kernel.org, riel@redhat.com, drepper@redhat.com
Subject: Re: OOM notifications
Date: Thu, 18 Oct 2007 22:38:21 +0200 [thread overview]
Message-ID: <4717C43D.6030204@keyaccess.nl> (raw)
In-Reply-To: <20071018202504.GA2854@dmt>
On 10/18/2007 10:25 PM, Marcelo Tosatti wrote:
> 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.
>
> Comments are more than welcome.
Given the desktop/embedded distinction you made, do you need both scenarios
active at the same time? If not, it seems something like a
echo -n <level> >/proc/sys/vm/danger
could do with just one sigdanger notification point? (with <level> suitably
defined as or in terms of the used threshold value).
Rene.
next prev parent reply other threads:[~2007-10-18 20:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 20:25 OOM notifications Marcelo Tosatti
2007-10-18 20:38 ` Rene Herman [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 20:15 Marcelo Tosatti
2007-10-26 21:02 ` Andrew Morton
2007-10-26 21:02 ` Andrew Morton
2007-10-26 21:05 ` Martin Bligh
2007-10-26 21:05 ` Martin Bligh
2007-10-26 21:11 ` Andrew Morton
2007-10-26 21:11 ` Andrew Morton
2007-10-26 21:35 ` Rik van Riel
2007-10-26 21:35 ` Rik van Riel
2007-10-26 21:59 ` Martin Bligh
2007-10-26 21:59 ` Martin Bligh
2007-10-26 22:30 ` Rik van Riel
2007-10-26 22:30 ` Rik van Riel
2007-10-28 21:16 ` Balbir Singh
2007-10-28 21:16 ` Balbir Singh
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
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=4717C43D.6030204@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.