On Wed, 2007-07-11 at 04:10 -0700, Paul Jackson wrote:
Or process or process groups, or all of the above :-)
One thing to think on though, we cannot have per process,uid,gid,pgrp
scheduling for one release only. So we'd have to manage interaction with
process containers. It might be that a simple weight multiplication
scheme is good enough:
weight = uid_weight * pgrp_weight * container_weight
Of course, if we'd only have a single level group scheduler (as was
proposed IIRC) it'd have to create intersection sets (as there might be
non trivial overlaps) based on these various weights and schedule these
resulting sets instead of the initial groupings.
-
