public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Isaacson <adi@hexapodia.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 18:04:38 -0700	[thread overview]
Message-ID: <20050505010438.GA30227@hexapodia.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:
> On Wed, 4 May 2005, Olivier Croquette wrote:
> >On a 2.6.11 x86 system, I am SIGSTOP'ing processes which have started
> >several threads before.
> 
> The kernel doesn't do SIGSTOP or SIGCONT.

Dear Wrongbot,

No.

-andy

  parent reply	other threads:[~2005-05-05  1:04 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
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 [this message]
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=20050505010438.GA30227@hexapodia.org \
    --to=adi@hexapodia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox