From: Hubertus Franke <frankeh@watson.ibm.com>
To: "Bill Abt" <babt@us.ibm.com>
Cc: drepper@redhat.com, linux-kernel@vger.kernel.org,
Martin.Wirth@dlr.de, pwaechtler@loewe-Komp.de,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] Futex Generalization Patch
Date: Wed, 10 Apr 2002 14:10:59 -0400 [thread overview]
Message-ID: <20020410191011.044393FE06@smtp.linux.ibm.com> (raw)
In-Reply-To: <OF5BCED6AA.E62C3259-ON85256B97.00624A9B@raleigh.ibm.com>
On Wednesday 10 April 2002 02:09 pm, Bill Abt wrote:
> On 04/10/2002 at 12:37:53 PM AST, Hubertus Franke <frankeh@watson.ibm.com>
>
> wrote:
> > Can somebody in the thread world weight in what there preferred mechanism
>
> is
>
> > regarding limits etc. Do you need to control the issue on how the signal
>
> is
>
> > delivered? Is a file descriptor good enough or you want a sys_call
>
> interface ?
>
>
> I went thru the POSIX specification and couldn't find any specified limits
> regarding this and in most cases these limits are enforced at the library
> level. It probably should be left up to the kernel folks to determine the
> kernel limits they can live with. The library can adapt to this value. I
> don't believe a pthread library would need any "extra" control of how the
> signal is delivered. A file descriptor is good enough, seems a waste to
> have to provide a sys_call interface.
>
So you are OK with having only poll or select. That seems odd.
It seems you still need SIGIO on your fd to get the async notification.
> Regards,
> Bill Abt
> Senior Software Engineer
> Next Generation POSIX Threading for Linux
> IBM Cambridge, MA, USA 02142
> Ext: +(00)1 617-693-1591
> T/L: 693-1591 (M/W/F)
> T/L: 253-9938 (T/Th/Eves.)
> Cell: +(00)1 617-803-7514
> babt@us.ibm.com or abt@us.ibm.com
> http://oss.software.ibm.com/developerworks/opensource/pthreads
-- Hubertus
--
-- Hubertus Franke (frankeh@watson.ibm.com)
next prev parent reply other threads:[~2002-04-10 19:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 18:09 [PATCH] Futex Generalization Patch Bill Abt
2002-04-10 18:10 ` Hubertus Franke [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-15 14:49 Bill Abt
2002-04-15 16:22 ` Hubertus Franke
2002-04-15 20:57 ` Mark Mielke
2002-04-15 20:46 ` Hubertus Franke
2002-04-16 20:03 ` Peter Wächtler
2002-04-10 19:59 Bill Abt
2002-04-10 20:14 ` Hubertus Franke
2002-04-11 13:55 ` Rusty Russell
2002-04-10 19:30 Bill Abt
2002-04-10 18:47 ` Hubertus Franke
2002-04-12 15:36 ` Peter Wächtler
2002-04-12 18:48 ` Hubertus Franke
2002-04-13 13:52 ` Peter Wächtler
2002-04-15 13:28 ` Hubertus Franke
2002-04-04 7:52 Rusty Russell
2002-04-04 16:28 ` Hubertus Franke
2002-04-06 9:48 ` Rusty Russell
2002-04-10 14:24 ` Hubertus Franke
2002-04-10 16:37 ` Rusty Russell
2002-04-10 16:37 ` Hubertus Franke
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=20020410191011.044393FE06@smtp.linux.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=Martin.Wirth@dlr.de \
--cc=babt@us.ibm.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pwaechtler@loewe-Komp.de \
--cc=rusty@rustcorp.com.au \
/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