[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830802191912t33cca90dx590791d9cdb29534@mail.gmail.com>
Date: Tue, 19 Feb 2008 19:12:05 -0800
From: "Paul Menage" <menage@...gle.com>
To: "Nick Andrew" <nick@...k-andrew.net>
Cc: trivial@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: Improve init/Kconfig help descriptions [PATCH 6/9]
On Feb 19, 2008 6:54 PM, Nick Andrew <nick@...k-andrew.net> wrote:
>
> config CGROUPS
> bool "Control Group support"
> help
> Control Groups enables processes to be tracked and grouped
> into "cgroups". This enables you, for example, to associate
> cgroups with certain CPU sets using "cpusets".
>
> When enabled, a new filesystem type "cgroup" is available
> and can be mounted to control cpusets and other
> resource/behaviour controllers.
>
> See <file:Documentation/cgroups.txt> for more information.
>
> If unsure, say N.
>
>
> I don't think that description is as clear as it could be. From
> the non-kernel-developer point of view, that is.
Originally this wasn't a user-selectable config value, it was
auto-selected by any subsystem that needed it. I think that was nicer
from the user-experience, and it would eliminate the need for this
documentation but there were concerns that this triggered unspecified
brokenness in the Kbuild system.
>
> Re "other resource/behaviour controllers", what in particular?
> I take it that our current controllers are cpusets, scheduler,
> CPU accounting and Resource counters?
Resource counters aren't a resource controller, they're a helper
library. The others are good examples, as is the memory controller
that's just been added to 2.6.25.
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists