[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0908281441340.7317@gentwo.org>
Date: Fri, 28 Aug 2009 14:43:34 -0400 (EDT)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
cc: Chris Friesen <cfriesen@...tel.com>,
raz ben yehuda <raziebe@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
peterz@...radead.org, maximlevitsky@...il.com, efault@....de,
riel@...hat.com, wiseman@...s.biu.ac.il,
linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: RFC: THE OFFLINE SCHEDULER
On Thu, 27 Aug 2009, Thomas Gleixner wrote:
> You are creating a "one special case" operation mode which is not
> justified in my opinion. Let's look at the problem you want to solve:
>
> Run exactly one thread on a dedicated CPU w/o any disturbance by the
> scheduler tick.
Thats not the problem I want to solve. There are multiple events that
could disturb a process like timers firing, softirqs and hardirqs.
> You can move away anything else than the scheduler tick from a CPU
> today already w/o a single line of code change.
How do you remove the per processor kernel threads for allocators and
other kernel subsystems? What about IPI broadcasts?
--
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