Re: [PATCH] Hookup group-scheduler with task container infrastructure

[Paul Menage]

On 9/10/07, Dmitry Adamushko <dmitry.adamushko@xxxxxxxxx> wrote:
> On 10/09/2007, Srivatsa Vaddagiri <vatsa@xxxxxxxxxxxxxxxxxx> wrote:
> > On Mon, Sep 10, 2007 at 10:22:59AM -0700, Andrew Morton wrote:
> > > objection ;)  "cpuctlr" isn't memorable.  Kernel code is write-rarely,
> > > read-often.  "cpu_controller", please.  The extra typing is worth it ;)
> >
> > Ok! Here's the modified patch (against 2.6.23-rc4-mm1).
>
> as everyone seems to be in a quest for a better name... I think, the
> obvious one would be just 'group_sched'.
>

But "sched" on its own could refer to CPU scheduling, I/O scheduling,
network scheduling, ...

And "group" is more or less implied by the fact that it's in the
containers/control groups filesystem.

So "group_sched" isn't really all that informative. The name should
definitely contain either "cpu" or "cfs".

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/