Re: [PATCH] cpuset and sched domains: sched_load_balance flag

[Nick Piggin <nickpiggin@yahoo.com.au>]

On Wednesday 03 October 2007 22:41, Paul Jackson wrote:
> > pdflush
> > is not pinned at all and can be dynamically created and destroyed. Ditto
> > for kjournald, as well as many others.
>
> Whatever is not pinned is moved out of the top cpuset, on the kind of
> systems I'm most familiar with.  They are put in a smaller cpuset, with
> load balancing, that is sized for the workload they might present, but
> kept separate from the main jobs.

So if a new pdflush is spawned, it get's moved to some cpuset? That
probably isn't something these realtime systems want to do (ie. the
non-realtime portion probably doesn't want to have any sort of scheduler
or even worry about cpusets at all).


> > Basically: it doesn't feel like a satisfactory solution to brush
> > these under the carpet.
>
> We don't do a whole lot of brushing under the carpet on these kind of
> systems.  If I gave you the impression we do, then I misled you - sorry.

No, not on your systems. I'm worried about the smaller ones that don't
get so much attention (eg. hard partitioning for realtime).