From: Mike Galbraith <efault@gmx.de>
To: paulmck@linux.vnet.ibm.com
Cc: Dimitri Sivanich <sivanich@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] rcu: Limit GP initialization to CPUs that have been online
Date: Fri, 16 Mar 2012 05:45:13 +0100 [thread overview]
Message-ID: <1331873113.7399.19.camel@marge.simpson.net> (raw)
In-Reply-To: <20120315170236.GF2381@linux.vnet.ibm.com>
On Thu, 2012-03-15 at 10:02 -0700, Paul E. McKenney wrote:
> On Thu, Mar 15, 2012 at 04:07:11AM +0100, Mike Galbraith wrote:
> > On Thu, 2012-03-15 at 03:42 +0100, Mike Galbraith wrote:
> > > On Wed, 2012-03-14 at 09:56 -0700, Paul E. McKenney wrote:
> > >
> > > > Does the following work better? It does pass my fake-big-system tests
> > > > (more testing in the works).
> > >
> > > Yup, tip booted fine. Thanks! I'll test, see if it gets upset.
> >
> > Wedged into 3.0 enterprise booted fine too, is now running rcutorture.
> > I'll add hotplug after it runs explosion free for a while. Any
> > suggestions for giving both virgin and 3.0 a thorough trouncing?
>
> It would be good to check the latency of RCU's grace-period
> initialization, and comparing the results with and without this patch.
> Dimitri might have scripting for that.
Yeah, I'll zoom in. Generic irqsoff tracing with rcutorture running
was... not the cleverest of ideas. (between fbcon and serial console, a
300us RCU blip would be a pimple on giants left butt cheek)
-Mike
next prev parent reply other threads:[~2012-03-16 4:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 0:24 [PATCH RFC] rcu: Limit GP initialization to CPUs that have been online Paul E. McKenney
2012-03-14 9:24 ` Mike Galbraith
2012-03-14 12:40 ` Mike Galbraith
2012-03-14 13:08 ` Dimitri Sivanich
2012-03-14 15:17 ` Paul E. McKenney
2012-03-14 16:56 ` Paul E. McKenney
2012-03-15 2:42 ` Mike Galbraith
2012-03-15 3:07 ` Mike Galbraith
2012-03-15 17:02 ` Paul E. McKenney
2012-03-15 17:21 ` Dimitri Sivanich
2012-03-16 4:45 ` Mike Galbraith [this message]
2012-03-15 17:59 ` Dimitri Sivanich
2012-03-16 7:27 ` Mike Galbraith
2012-03-16 8:09 ` Mike Galbraith
2012-03-16 8:45 ` Mike Galbraith
2012-03-16 17:28 ` Dimitri Sivanich
2012-03-16 17:51 ` Paul E. McKenney
2012-03-16 17:56 ` Dimitri Sivanich
2012-03-16 19:11 ` Mike Galbraith
2012-03-22 15:35 ` Mike Galbraith
2012-03-22 20:24 ` Dimitri Sivanich
2012-03-23 4:48 ` Mike Galbraith
2012-03-23 19:23 ` Paul E. McKenney
2012-04-11 11:04 ` Mike Galbraith
2012-04-13 18:42 ` Paul E. McKenney
2012-04-14 5:42 ` Mike Galbraith
2012-03-15 17:58 ` Dimitri Sivanich
2012-03-15 18:23 ` Paul E. McKenney
2012-03-15 21:07 ` Paul E. McKenney
2012-03-16 15:46 ` Dimitri Sivanich
2012-03-16 17:21 ` Paul E. McKenney
2012-03-14 17:07 ` Mike Galbraith
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=1331873113.7399.19.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sivanich@sgi.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 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.