Messages in this thread | | | Subject | Re: [PATCH RFC] rcu: Limit GP initialization to CPUs that have been online | From | Mike Galbraith <> | Date | Fri, 16 Mar 2012 05:45:13 +0100 |
| |
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
| |