Re: [PATCH] cpuset: Rework sched domains and CPU hotplug handling (2.6.27-rc1)

[Max Krasnyansky <maxk@qualcomm.com>]

Paul Jackson wrote:
> Max wrote:
>> But it does seem like an overkill to schedule a workqueue ...
> 
> "overkill" -- by what metric?
> 
> If something is overkill, it means something is excessive.
> Excess (and deficiency) occur along some scale, some metric.
> 
> If not by CPU cycles, then by what metric is it overkill?
> 

Paul, I think you're focusing on the wrong part of my reply ;-).
You are, of course, correct about the overkill metric. I was saying
that saving cycles in that path was not my goal when I wrote
the patch. I just added necessary functions to make existing paths
work they way they currently do and only changed one path because
it had to change due to lock nesting issues.
Along the way simply pointed it out that scheduling work unnecessarily
does seem less efficient. That was not the important part though :)

Max