From: Andrew Morton <akpm@linux-foundation.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
josh@freedesktop.org, dipankar@in.ibm.com
Subject: Re: [PATCH] Force rcutorture tasks to spread over CPUs
Date: Tue, 26 Jun 2007 16:13:17 -0700 [thread overview]
Message-ID: <20070626161317.767d5ec0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070613042804.GA6132@linux.vnet.ibm.com>
On Tue, 12 Jun 2007 21:28:04 -0700
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> + while (!startwriters)
> + barrier(); /* Force scheduler to spread over CPUs. */
one wonders whether a cpu_relax() would be a bit nicer here. That implicitly
does a barrier().
This patch doesn't make much sense for non-SMP builds?
next prev parent reply other threads:[~2007-06-26 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 4:28 [PATCH] Force rcutorture tasks to spread over CPUs Paul E. McKenney
2007-06-13 16:49 ` Josh Triplett
2007-06-26 23:13 ` Andrew Morton [this message]
2007-06-27 6:30 ` Ingo Molnar
2007-06-27 16:30 ` Paul E. McKenney
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=20070626161317.767d5ec0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
/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