From: Chris Wright <chrisw@osdl.org>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Chris Wright <chrisw@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Pollable Semaphores
Date: Sat, 22 Jan 2005 10:02:03 -0800 [thread overview]
Message-ID: <20050122100203.N24171@build.pdx.osdl.net> (raw)
In-Reply-To: <a36005b50501212339405ca4a7@mail.gmail.com>; from drepper@gmail.com on Fri, Jan 21, 2005 at 11:39:55PM -0800
* Ulrich Drepper (drepper@gmail.com) wrote:
> On Fri, 21 Jan 2005 23:05:04 -0800, Chris Wright <chrisw@osdl.org> wrote:
> > Yeah, here it is. I refreshed it against a current kernel. It passes my
> > same old test, where I select on /proc/<pid>/status fd in exceptfds.
>
> Looks certainly attractive to me. Nice small patch. How quickly
> after the death of the process is proc_pid_flush() called?
I don't think it's called until it's reaped.
> If this could go in and the futex stuff is handled, there is "only"
> async I/O to handle. After that we could finally create a uniform
> event mechanism at userlevel which binds all these events (I/O,
> process/thread termination, sync primitives) together. Maybe support
> for legacy sync primitives (SysV semaphores, msg queues) is needed as
> well, don't know yet. Note that I assume that polling of POSIX
> mqueues works as it did the last time I tried it.
It should, AFAIK nothing there has changed.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-22 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 21:22 Pollable Semaphores Brandon Corey
2005-01-21 21:37 ` Roland Dreier
2005-01-21 23:17 ` Brent Casavant
2005-01-22 3:43 ` Ulrich Drepper
2005-01-22 5:52 ` Chris Wright
2005-01-22 7:05 ` Chris Wright
2005-01-22 7:39 ` Ulrich Drepper
2005-01-22 18:02 ` Chris Wright [this message]
2005-01-24 20:42 ` Robert White
2005-01-22 0:07 ` 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=20050122100203.N24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.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