From: Tejun Heo <tj@kernel.org>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH] improve stop_machine performance
Date: Fri, 05 Mar 2010 23:17:46 +0900 [thread overview]
Message-ID: <4B91128A.5000305@kernel.org> (raw)
In-Reply-To: <20100305141143.GA17417@sgi.com>
Hello,
On 03/05/2010 11:11 PM, Dimitri Sivanich wrote:
> It seems reasonable as long as setup is fast enough. Will that
> thread indeed become fully uninterruptible (not affected by anything
> including scheduler decisions like
> sched_rt_period_us/sched_rt_runtime_us, etc..)?
I think so. They basically are used to do the same thing - occupying
the CPU. I'll give a shot. Please give me a couple of days.
Thanks.
--
tejun
prev parent reply other threads:[~2010-03-05 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 21:20 [PATCH] improve stop_machine performance Dimitri Sivanich
2010-03-05 0:22 ` Tejun Heo
2010-03-05 14:11 ` Dimitri Sivanich
2010-03-05 14:17 ` Tejun Heo [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=4B91128A.5000305@kernel.org \
--to=tj@kernel.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sivanich@sgi.com \
--cc=torvalds@linux-foundation.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