From: "Ulrich Drepper" <drepper@gmail.com>
To: "Michael Kerrisk" <mtk.manpages@googlemail.com>
Cc: "Ulrich Drepper" <drepper@redhat.com>,
"Davide Libenzi" <davidel@xmailserver.org>,
lkml <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jakub Jelinek" <jakub@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Rationale for paccept() sigset argument?
Date: Mon, 1 Sep 2008 17:48:44 -0700 [thread overview]
Message-ID: <a36005b50809011748j75b1984ar844252a57f7e1d50@mail.gmail.com> (raw)
In-Reply-To: <48AC4B44.2010606@gmail.com>
On Wed, Aug 20, 2008 at 9:50 AM, Michael Kerrisk
<mtk.manpages@googlemail.com> wrote:
> What is the rationale for the sigset argument of paccept()?
accept, like select/poll, is used often as a function to dealy
operation. Unlike read, recv, etc, which are handled using O_NONBLOCK
and select/poll. pselect/ppoll do not really have a sigset parameter
to handle signals in general. You use it to enable special handling
in case of blocking. Example: if you want to implement userlevel
context switching, you dedicate a signal to wake up any blocked
thread. Since accept falls more into the same category than poll,
this means the sigset parameter is justified. In theory we could add
it to all functions but there is no reason to do this without any
other reason to change the interface.
next prev parent reply other threads:[~2008-09-02 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 16:50 Rationale for paccept() sigset argument? Michael Kerrisk
2008-08-29 20:45 ` Michael Kerrisk
2008-09-02 0:48 ` Ulrich Drepper [this message]
2008-09-02 7:58 ` Michael Kerrisk
2008-09-08 13:33 ` Michael Kerrisk
2008-09-11 5:48 ` Michael Kerrisk
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=a36005b50809011748j75b1984ar844252a57f7e1d50@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).