[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070611073634.GB32446@elte.hu>
Date: Mon, 11 Jun 2007 09:36:34 +0200
From: Ingo Molnar <mingo@...e.hu>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Dinakar Guniguntala <dino@...ibm.com>
Subject: Re: v2.6.21.4-rt11
* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
> 2.6.21.4-rt12 boots on 4-CPU Opteron and passes several hours of
> rcutorture. However, if I simply do "modprobe rcutorture", the kernel
> threads do not spread across the CPUs as I would expect them to, even
> given CFS. Instead, the readers all stack up on a single CPU, and I
> have to use the "taskset" command to spread them out manually. Is
> there some config parameter I am missing out on?
hm, what affinity do they start out with? Could they all be pinned to
CPU#0 by default?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists