Re: [PATCH 11/32] nohz/cpuset: Don't turn off the tick if rcu needs it

[Gilad Ben-Yossef]

On Wed, Mar 28, 2012 at 2:21 PM, Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:
> On Wed, Mar 28, 2012 at 09:55:37AM +0200, Gilad Ben-Yossef wrote:
|
>> At the risk of butting in on this little flame war, I think it is
>> worth mentioning
>> that this discussion arouse in the context of of a feature
>> (cpuset/nohz) that deals
>> with a single task running alone on a CPU and making zero use of
>> kernel services,
>> from scheduling, through interrupts, to system calls. It's just a pure
>> 100% cpu  bound task.
>
> Note that cpu isolation is a specific usecase of nohz cpusets. But it's
> intended to be more generally useful (probably for most workloads). That
> means we really want to support syscalls, interrupts and everything. That's
> why it is called adaptive tickless and not just userspace isolated tickless.

Point taken.  I guess I suffer from myopic vision just like the next guy  :-)

Gilad

-- 
Gilad Ben-Yossef
Chief Coffee Drinker
gilad@xxxxxxxxxxxxx
Israel Cell: +972-52-8260388
US Cell: +1-973-8260388
http://benyossef.com

"If you take a class in large-scale robotics, can you end up in a
situation where the homework eats your dog?"
 -- Jean-Baptiste Queru
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/