public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Ray Bryant <raybry@sgi.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ia64@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 16:51:59 +0000	[thread overview]
Message-ID: <jept25yggg.fsf@sykes.suse.de> (raw)
In-Reply-To: <20041122162214.GE21861@wotan.suse.de> (Andi Kleen's message of "Mon, 22 Nov 2004 17:22:14 +0100")

Andi Kleen <ak@suse.de> writes:

> At least in traditional signal semantics you have to call sigaction
> or signal in each signal handler to reset the signal. So that 
> assumption is not necessarily true.

If you use sigaction then you get POSIX semantics, which don't have this
problem.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2004-11-22 16:51 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 [this message]
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
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=jept25yggg.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=ak@suse.de \
    --cc=bls@sgi.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 \
    /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