[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070611011954.GG27982@linux.vnet.ibm.com>
Date: Sun, 10 Jun 2007 18:19:54 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
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
On Sat, Jun 09, 2007 at 11:05:07PM +0200, Ingo Molnar wrote:
>
> i'm pleased to announce the v2.6.21.4-rt11 kernel, which can be
> downloaded from the usual place:
>
> http://people.redhat.com/mingo/realtime-preempt/
>
> more info about the -rt patchset can be found in the RT wiki:
>
> http://rt.wiki.kernel.org
>
> -rt11 is a bit more experimental than usual: it includes the CFS
> scheduler. Several people have suggested the inclusion of CFS into the
> -rt tree: the determinism of the CFS scheduler is a nice match to the
> determinism offered by PREEMPT_RT. The port of CFS to -rt was done by
> Dinakar Guniguntala. Tested on i686 and x86_64.
>
> to build a 2.6.21.4-rt11 tree, the following patches should be applied:
>
> http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.4.tar.bz2
> http://people.redhat.com/mingo/realtime-preempt/patch-2.6.21.4-rt11
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?
Thanx, Paul
-
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