Messages in this thread |  | | Date | Thu, 30 Nov 2006 00:08:36 -0800 | From | "Paul Menage" <> | Subject | Re: [RFC] dynsched - different cpu schedulers per cpuset |
| |
On 11/29/06, Paul Jackson <pj@sgi.com> wrote: > > Your dynamic scheduler mechanisms appear (from what I can tell after a > brief glance) to be a candidate for being such a controller.
Possibly, if it was some kind of multi-level scheduler - i.e. a top-level scheduler picks which container to run, and then a configurable per-container scheduler picks a task from that container.
But (having glanced at the code even less than you) it sounded like it was intended to be a single level scheduler, configured on a per-cpu basis. In that case tying it to (exclusive) cpusets sounds like it might be more reasonable.
Paul. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |