Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller

From: Srivatsa Vaddagiri
Date: Fri Aug 04 2006 - 02:49:40 EST

On Thu, Aug 03, 2006 at 10:36:50PM -0700, Andrew Morton wrote:
> ug, I didn't know this. Had I been there (sorry) I'd have disagreed with
> this whole strategy.
> I thought the most recently posted CKRM core was a fine piece of code. It
> provides the machinery for grouping tasks together and the machinery for
> establishing and viewing those groupings via configfs, and other such
> common functionality. My 20-minute impression was that this code was an
> easy merge and it was just awaiting some useful controllers to come along.
> And now we've dumped the good infrastructure and instead we've contentrated
> on the controller, wired up via some imaginative ab^H^Hreuse of the cpuset
> layer.

CPUset was used in this patch series primarily because it
represent a task-grouping mechanism already in the kernel and because
people at the BoF wanted to start with something simple. The idea of using
cpusets here was not to push this as a final solution, but use it as a means to
discuss the effects of task-grouping on CPU scheduler.

We had be more than happy to work with the ckrm core which was posted last.
In fact I had sent out the same cpu controller against ckrm core itself last
time around to Nick/Ingo.

> Right. We won't be controlling memory, numtasks, disk, network etc
> controllers via cpusets, will we?

Agreed. Using CPUset interface makes sense mainly for cpu and memory.

> Correct me if I'm wrong, but a cpuset isn't the appropriate machinery to be
> using to group tasks.
> And if this whole resource-control effort is to end up being successful, it
> should have as core infrastructure a flexible, appropriate and uniform way
> of grouping tasks together and of getting data into and out of those
> aggregates. We already have that, don't we?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at