On Mon, Jun 11, 2007 at 08:55:27AM -0700, Paul E. McKenney wrote:

On Mon, Jun 11, 2007 at 05:38:55PM +0200, Ingo Molnar wrote:

quoted

* Paul E. McKenney [off-list ref] wrote:

quoted

quoted

hm, what affinity do they start out with? Could they all be pinned 
to CPU#0 by default?

They start off with affinity masks of 0xf on a 4-CPU system.  I would 
expect them to load-balance across the four CPUs, but they stay all on 
the same CPU until long after I lose patience (many minutes).

ugh. Would be nice to figure out why this happens. I enabled rcutorture 
on a dual-core CPU and all the threads are spread evenly.

Here is the /proc/cpuinfo in case this helps.  I am starting up a test
on a dual-core CPU to see if that works better.

And this quickly load-balanced to put a pair of readers on each CPU.
Later, it moved one of the readers so that it is now running with
one reader on one of the CPUs, and the remaining three readers on the
other CPU.

Argh...  this is with 2.6.21-rt1...  Need to reboot with 2.6.21.4-rt12...

						Thanx, Paul