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 13:31:25 -0400 [thread overview]
Message-ID: <20071030133125.3458420c@cuia.boston.redhat.com> (raw)
In-Reply-To: <20071030155525.GF9702@duck.suse.cz>
On Tue, 30 Oct 2007 16:55:25 +0100
Jan Kara <jack@suse.cz> wrote:
> Hmm, that's right, but still the kernel->userspace interface could be via
> netlink (which is much more flexible than signals etc.) and then in userspace
> we could implement also some simple interface (UNIX socket?) for server like
> apps...
I think we all agree that it should not be a Unix signal, if only
because glibc cannot manipulate memory pools from signal handlers :)
The low memory message (for lack of a better word) needs to get to
userspace over a file descriptor, which the process can select() or
poll() on from its main loop.
Whether that is a device node, a sysfs file, a netlink socket or
something else ... I don't particularly care :)
--
All Rights Reversed
next prev parent reply other threads:[~2007-10-30 17:31 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
2007-10-30 15:55 ` Jan Kara
2007-10-30 17:31 ` Rik van Riel [this message]
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=20071030133125.3458420c@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®