From: Davide Libenzi <davidel@xmailserver.org>
To: Davi Arnaut <davi@haxent.com.br>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] signalfd: retrieve multiple signals with one read() call
Date: Sun, 20 May 2007 12:17:21 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705201208190.19325@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <464F912F.3040205@haxent.com.br>
On Sat, 19 May 2007, Davi Arnaut wrote:
> Hi,
>
> Gathering signals in bulk enables server applications to drain a signal
> queue (almost full of realtime signals) more efficiently by reducing the
> syscall and file look-up overhead.
>
> Very similar to the sigtimedwait4() call described by Niels Provos,
> Chuck Lever, and Stephen Tweedie in a paper entitled "Analyzing the
> Overload Behavior of a Simple Web Server". The paper lists more details
> and advantages.
That paper is a pre-epoll thing. Nowadays I see no value in using RT
signals as main event gathering mechanism ;)
> Signed-off-by: Davi E. M. Arnaut <davi@haxent.com.br>
The patch looks otherwise good to me, and I see no reasons why we
shoulnd't be fetching more than one signal if available.
Acked-by: Davide Libenzi <davidel@xmailserver.org>
- Davide
next prev parent reply other threads:[~2007-05-20 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 0:07 Davi Arnaut
2007-05-20 19:17 ` Davide Libenzi [this message]
2007-05-21 4:02 ` Andrew Morton
2007-05-21 4:14 ` Davide Libenzi
2007-05-21 4:20 ` Davide Libenzi
2007-05-21 4:26 ` Andrew Morton
2007-05-21 5:05 ` Davide Libenzi
2007-05-21 5:12 ` Andrew Morton
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=Pine.LNX.4.64.0705201208190.19325@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=davi@haxent.com.br \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®