From: ern0 <ern0@linkbroker.hu>
To: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: Slow signal delivery to server process with heavy I/O
Date: Mon, 12 Jul 2010 09:06:49 +0200 [thread overview]
Message-ID: <4C3ABF09.3090808@linkbroker.hu> (raw)
In-Reply-To: <19514.33382.135366.743597@cerise.gclements.plus.com>
> The kernel selects one thread which hasn't blocked the signal.
So if you want to catch signals ASAP, is it a good strategy to
- leave one thread for signal catching, it may perform sleeps;
- other threads should block all signals?
--
ern0
dataflow programmer & evangelist
next prev parent reply other threads:[~2010-07-12 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 23:08 Slow signal delivery to server process with heavy I/O Dallas Clement
[not found] ` <AANLkTin9wvP1p3rp3Lv6-APEfvq9jZACF0TEas9a2f6l@mail.gmail.com>
2010-07-10 23:46 ` Dallas Clement
2010-07-11 13:18 ` Glynn Clements
2010-07-11 22:56 ` Dallas Clement
2010-07-12 2:48 ` Glynn Clements
2010-07-12 7:06 ` ern0 [this message]
2010-07-12 16:14 ` Glynn Clements
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=4C3ABF09.3090808@linkbroker.hu \
--to=ern0@linkbroker.hu \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).