From: Casey Dahlin <cdahlin@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Scott James Remnant <scott@netsplit.com>
Subject: Re: [RFC PATCH] waitfd: file descriptor to wait on child processes
Date: Tue, 09 Dec 2008 13:46:59 -0500 [thread overview]
Message-ID: <493EBD23.3020800@redhat.com> (raw)
In-Reply-To: <20081209170543.59b4fb73@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> prototype for a fourth: waitfd. It pretty much does what the name
>> suggests: reading from it yields a series of status ints (as would be
>> written into the second argument of waitpid) for child processes that
>> have changed state. It takes essentially the same arguments as waitpid
>> (for now) and supports the same set of features.
>>
>
> This propogates the fundamental braindamage of waitpid - the fact the
> notification only works on child process trees.
>
> Here is a more elegant suggestion - use epoll, inotify and friends fully
> on /proc process nodes.
>
> Alan
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Last I checked inotify was not supported in /proc, or at least most of
it. What kind of work load is it to change that?
--CJD
next prev parent reply other threads:[~2008-12-09 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 17:00 [RFC PATCH] waitfd: file descriptor to wait on child processes Casey Dahlin
2008-12-09 17:05 ` Alan Cox
2008-12-09 17:12 ` Scott James Remnant
2008-12-09 18:46 ` Casey Dahlin [this message]
2008-12-09 19:04 ` Alan Cox
2008-12-09 19:21 ` Casey Dahlin
2008-12-09 19:41 ` Davide Libenzi
2008-12-09 20:09 ` Casey Dahlin
2008-12-12 23:28 ` Scott James Remnant
2008-12-13 4:29 ` Davide Libenzi
2008-12-13 8:43 ` Scott James Remnant
2008-12-13 18:39 ` Davide Libenzi
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=493EBD23.3020800@redhat.com \
--to=cdahlin@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@netsplit.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