From: Andi Kleen <ak@suse.de>
To: "Boehm, Hans" <hans.boehm@hp.com>
Cc: Ray Bryant <raybry@sgi.com>, Andi Kleen <ak@suse.de>,
Andreas Schwab <schwab@suse.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org,
lse-tech <lse-tech@lists.sourceforge.net>,
holt@sgi.com, Dean Roe <roe@sgi.com>, Brian Sumner <bls@sgi.com>,
John Hawkes <hawkes@tomahawk.engr.sgi.com>
Subject: Re: [Lse-tech] scalability of signal delivery for Posix Threads
Date: Mon, 22 Nov 2004 21:34:48 +0000 [thread overview]
Message-ID: <20041122213448.GA16153@wotan.suse.de> (raw)
In-Reply-To: <65953E8166311641A685BDF71D865826058B5C@cacexc12.americas.cpqcorp.net>
> I think this is a more general issue. Special casing one
It just cannot be done in the general case without slowing
down sigaction significantly. Or maybe it can, but nobody
has proposed a way to do it so far.
It's difficult to design for machines where a simple spinlock
doesn't work properly anymore.
> piece of it is only going to make performance more surprising,
> something I think should be avoided if at all possible.
The special case in particular would be signals directed to a specific TID;
compared to signals load balanced over the thread group which needs
shared writable state. To simplify the fast path you could also make
more simplications: no queueing (otherwise you would need to duplicate
a lot of state to handle that into the task_struct) and probably
no SIGCHILD which is also full of special cases.
-And
next prev parent reply other threads:[~2004-11-22 21:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:51 scalability of signal delivery for Posix Threads Ray Bryant
2004-11-22 16:07 ` Matthew Wilcox
2004-11-22 19:49 ` [Lse-tech] " Ray Bryant
2004-11-22 19:53 ` Andi Kleen
2004-11-22 16:22 ` [Lse-tech] " Andi Kleen
2004-11-22 16:51 ` Andreas Schwab
2004-11-22 16:54 ` Andi Kleen
2004-11-22 18:56 ` Ray Bryant
2004-11-22 19:22 ` Ray Bryant
2004-11-22 17:23 ` Philip J. Mucci
2004-11-22 21:26 ` Boehm, Hans
2004-11-22 21:34 ` Andi Kleen [this message]
2004-12-01 22:53 ` Brent Casavant
2004-11-22 21:27 ` Rick Lindsley
2004-11-22 23:39 ` Ray Bryant
2004-11-22 23:01 ` Boehm, Hans
2004-11-22 17:19 ` Robin Holt
2004-11-22 19:25 ` Ray Bryant
2004-11-23 20:42 ` Ray Bryant
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=20041122213448.GA16153@wotan.suse.de \
--to=ak@suse.de \
--cc=bls@sgi.com \
--cc=hans.boehm@hp.com \
--cc=hawkes@tomahawk.engr.sgi.com \
--cc=holt@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=raybry@sgi.com \
--cc=roe@sgi.com \
--cc=schwab@suse.de \
/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