Paul M wrote:
> Even if the resource control portions aren't totally compatible,
> having two separate process container abstractions in the kernel is
> sub-optimal
At heart, CKRM (ne Resource Groups) are (well, have been until now)
different than cpusets.
Cpusets answers the question 'where', and Resource Groups 'how much'.
The fundamental motivation behind cpusets was to be able to enforce
job isolation. A job can get dedicated use of specified resources,
-even- if it means those resources are severely underutilized by that
job.
The fundamental motivation (Chandra or others correct me if I'm wrong)
of Resource Groups is to improve capacity utilization while limiting
starvation due to greedy, competing users for the same resources.
Cpusets seeks maximum isolation. Resource Groups seeks maximum
capacity utilization while preserving guaranteed levels of quality
of service.
Cpusets are that wall between you and the neighbor you might not
trust. Resource groups are a large family of modest wealth sitting
down to share a meal.
It seems that cpusets can mimic memory resource groups. I don't
see how cpusets could mimic other resource groups. But maybe I'm
just being a dimm bulb.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
