From: Jeff Dike <jdike@karaya.com>
To: Corey Minyard <minyard@acm.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Threads performance - allow signal handler to not call handler
Date: Wed, 27 Mar 2002 17:02:44 -0500 [thread overview]
Message-ID: <200203272202.RAA04496@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Wed, 27 Mar 2002 15:46:01 CST." <3CA23D99.6030900@acm.org>
minyard@acm.org said:
> With this patch, if the flag is set, the signal handler won't get
> called (thus saving the overhead of going in and out of userland for
> the handler), but it will still wake up sigsuspend() and select().
I've wanted this for UML as well. I have some empty signal handlers which
exist for no reason other than to wake up pause/sigsuspend/et al.
Jeff
prev parent reply other threads:[~2002-03-27 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 21:46 [patch] Threads performance - allow signal handler to not call handler Corey Minyard
2002-03-27 22:02 ` Jeff Dike [this message]
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=200203272202.RAA04496@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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