Re: [RFC] dynsched - different cpu schedulers per cpuset

On 11/29/06, Paul Jackson <pj@xxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [ckrm-tech] [RFC] [PATCH 0/3] Add group fairness to CFS
    ... I am inclined to have the core scheduler support atleast two levels ... of hierarchy (to better isolate each container) and resort to the ... hierarchy in pieces so that n levels of hierarchy become k levels of n/k ... Hybrid schemes will still incur the difficulties of hierarchical ...
    (Linux-Kernel)
  • Re: [ckrm-tech] [RFC] [PATCH 0/3] Add group fairness to CFS
    ... inserted in rb-tree much to the left of those 1000 tasks (and which indirectly ... level hierarchical scheduling inside the core scheduler). ... I am inclined to have the core scheduler support atleast two levels of ... hierarchy (to better isolate each container) and resort to the flattening ...
    (Linux-Kernel)
  • Re: [RFC] dynsched - different cpu schedulers per cpuset
    ... configurable per-container scheduler picks a task from that container. ... possible to integrate into your CPU Controller. ... In that case tying it to cpusets sounds like it ...
    (Linux-Kernel)