From: Daniel Jacobowitz <dan@debian.org>
To: "Richard B. Johnson" <linux-os@analogic.com>
Cc: Olivier Croquette <ocroquette@free.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler: SIGSTOP on multi threaded processes
Date: Wed, 4 May 2005 15:16:04 -0400 [thread overview]
Message-ID: <20050504191604.GA29730@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0505041403310.21458@chaos.analogic.com>
On Wed, May 04, 2005 at 02:16:24PM -0400, Richard B. Johnson wrote:
> The kernel doesn't do SIGSTOP or SIGCONT. Within init, there is
> a SIGSTOP and SIGCONT handler. These can be inherited by others
> unless changed, perhaps by a 'C' runtime library. Basically,
> the SIGSTOP handler executes pause() until the SIGCONT signal
> is received.
>
> Any delay in stopping is the time necessary for the signal to
> be delivered. It is possible that the section of code that
> contains the STOP/CONT handler was paged out and needs to be
> paged in before the signal can be delivered.
>
> You might quicken this up by installing your own handler for
> SIGSTOP and SIGCONT....
I don't know what RTOSes you've been working with recently, but none of
the above is true for Linux. I don't think it ever has been.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-04 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 17:37 Scheduler: SIGSTOP on multi threaded processes Olivier Croquette
2005-05-04 18:16 ` Richard B. Johnson
2005-05-04 19:16 ` Daniel Jacobowitz [this message]
2005-05-04 21:06 ` Alex Riesen
2005-05-05 0:42 ` Richard B. Johnson
2005-05-05 0:33 ` Richard B. Johnson
2005-05-05 0:45 ` Richard B. Johnson
2005-05-05 12:24 ` Richard B. Johnson
2005-05-05 13:14 ` Denis Vlasenko
2005-05-05 13:30 ` Andreas Schwab
2005-05-05 22:04 ` Miquel van Smoorenburg
2005-05-06 23:15 ` Problem while stopping many threads within a module Yuly Finkelberg
2006-04-20 8:43 ` shikha
2005-05-10 20:59 ` Scheduler: SIGSTOP on multi threaded processes Olivier Croquette
2005-05-10 21:12 ` Roland McGrath
2005-05-11 18:58 ` Olivier Croquette
2005-05-10 23:05 ` Alex Riesen
2005-05-05 1:04 ` Andy Isaacson
2005-05-04 19:10 ` Alexander Nyberg
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=20050504191604.GA29730@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=ocroquette@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.