From: Christopher Smith <x@xman.org>
To: "Daniel R. Kegel" <dank@alumni.caltech.edu>, balbir.singh@wipro.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: A signal fairy tale
Date: Fri, 29 Jun 2001 01:18:10 -0700 [thread overview]
Message-ID: <5.1.0.14.0.20010629011647.02a00a98@imap.xman.org> (raw)
In-Reply-To: <200106280249.TAA06507@alumnus.caltech.edu>
At 07:49 PM 6/27/2001 -0700, Daniel R. Kegel wrote:
>Balbir Singh <balbir.singh@wipro.com> wrote:
> >sigopen() should be selective about the signals it allows
> >as argument. Try and make sigopen() thread specific, so that if one
> >thread does a sigopen(), it does not imply it will do all the signal
> >handling for all the threads.
>
>IMHO sigopen()/read() should behave just like sigwait() with respect
>to threads. That means that in Posix, it would not be thread specific,
>but in Linux, it would be thread specific, because that's how signals
>and threads work there at the moment.
Actually, I believe with IBM's new Posix threads implementation, Linux
finally does signal delivery "the right way". In general, I think it'd be
nice if this API *always* sucked up signals from all threads. This makes
sense particularly since the FD is accessible by all threads.
--Chris
next prev parent reply other threads:[~2001-06-29 8:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 2:49 Daniel R. Kegel
2001-06-29 8:18 ` Christopher Smith [this message]
2001-06-29 9:05 ` Dan Kegel
[not found] <fa.d69j5vv.ej8irj@ifi.uio.no>
[not found] ` <fa.h2rpibv.87m5bp@ifi.uio.no>
2001-06-28 14:59 ` Dan Maas
2001-06-28 15:21 ` Alan Cox
2001-06-29 8:26 ` Christopher Smith
2001-06-29 11:56 ` Chris Wedgwood
2001-06-30 10:02 ` Jan Hudec
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 20:11 Daniel R. Kegel
2001-06-29 8:31 ` Christopher Smith
2001-06-28 3:04 Daniel R. Kegel
2001-06-28 14:46 ` Jamie Lokier
2001-06-28 2:57 Daniel R. Kegel
2001-06-29 8:19 ` Christopher Smith
2001-06-29 9:29 ` Dan Kegel
2001-06-29 18:46 ` Dan Kegel
2001-07-02 22:33 ` Christopher Smith
2001-06-26 12:54 Dan Kegel
2001-06-27 3:56 ` Christopher Smith
2001-06-27 6:21 ` Balbir Singh
2001-06-27 18:11 ` Christopher Smith
2001-06-28 3:28 ` Balbir Singh
2001-06-27 9:18 ` Jamie Lokier
2001-06-27 18:16 ` Christopher Smith
2001-06-28 12:58 ` John Fremlin
2001-06-28 16:21 ` Jamie Lokier
2001-06-29 8:22 ` Christopher Smith
2001-06-29 11:47 ` John Fremlin
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=5.1.0.14.0.20010629011647.02a00a98@imap.xman.org \
--to=x@xman.org \
--cc=balbir.singh@wipro.com \
--cc=dank@alumni.caltech.edu \
--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
all inboxes | Powered by JetHome®