 Messages in this thread On Tue, 2009-12-08 at 21:23 +0900,
Tejun Heo wrote: > On 12/08/2009 09:10 PM, Peter Zijlstra wrote:
> > Hotplug and deterministic are not to be used in the same
sentence, its > > an utter slow path and I'd much rather have
simple code than clever code > > there -- there's been way too
many 'interesting' hotplug problems. > Slow and indeterminism
comes in different magnitudes.  Determinism does _not_ come in
magnitudes, its a very binary property, either it is or it is
not.  As to the order of slowness for unplug, that is about
maximal, its _the_ slowest path in the whole kernel.  > >
Furthermore if it's objective is to cater to generic thread
pools then I > > think its an utter fail simply because it
mandates strict cpu affinity, > > that basically requires you to
write a work scheduler to balance work > > load etc.. Much
easier is a simple unbounded thread pool that gets > > balanced
by the regular scheduler. > The observation was that for most
long running async jobs, most time > is