From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Eric Smith" <eric@brouhaha.com>
Cc: linux-kernel@vger.kernel.org, "Andi Kleen" <andi@firstfloor.org>
Subject: Re: Any lightweight way for one thread to force another thread to suspend execution?
Date: Sun, 22 Jun 2008 08:33:51 +0200 [thread overview]
Message-ID: <e2e108260806212333q669a0ae5o9df105652352ae89@mail.gmail.com> (raw)
In-Reply-To: <49370.71.139.37.220.1214099737.squirrel@ruckus.brouhaha.com>
On Sun, Jun 22, 2008 at 3:55 AM, Eric Smith <eric@brouhaha.com> wrote:
> Andi wrote:
>> Any such mechanism will need a syscall, and it's unlikely that
>> any syscall will get much cheaper than a kill(SIGSTOP)
>
> But is there a way for the process sending the SIGSTOP to wait until it
> has taken effect? I need a method to *synchronously* stop another
> thread. That's why I thought I probably needed something more
> elaborate than SIGSTOP, though I'd like to minimize the number of
> system calls required.
Are you aware that SIGSTOP suspends all the threads in a process
instead of a single thread ? (Note: this is how the NPTL behaves. With
LinuxThreads it was possible to suspend a single thread via SIGSTOP,
but this was a violation of the POSIX standards.)
Bart.
next prev parent reply other threads:[~2008-06-22 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 23:54 Eric Smith
2008-06-21 14:04 ` Andi Kleen
2008-06-22 1:55 ` Eric Smith
2008-06-22 6:33 ` Bart Van Assche [this message]
2008-06-22 9:14 ` Jan Engelhardt
2008-06-23 21:08 ` Eric Smith
2008-06-24 7:59 ` Mikael Pettersson
2008-06-21 16:38 ` Bart Van Assche
2008-06-22 2:02 ` Eric Smith
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=e2e108260806212333q669a0ae5o9df105652352ae89@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=andi@firstfloor.org \
--cc=eric@brouhaha.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®