On Wed, Feb 20, 2008 at 01:06:09AM +1100, Nick Andrew wrote:
> Here is a series of 9 patches to init/Kconfig intended to improve the
> usefulness and consistency of the help descriptions. The patches are
> against linux-2.6.24.2.
> [...]
> Patch 6
> CGROUPS
> CGROUP_DEBUG
> CPUSETS
> FAIR_GROUP_SCHED
> FAIR_CGROUP_SCHED
> CGROUP_CPUACCT
> PROC_PID_CPUSET
Changelog:
Improve usefulness and consistency of kernel configuration help messages.
Signed-off-by: Nick Andrew <[EMAIL PROTECTED]>
--- a/init/Kconfig 2008-02-20 00:45:07.000000000 +1100
+++ b/init/Kconfig 2008-02-20 00:52:07.000000000 +1100
@@ -289,10 +289,16 @@ config LOG_BUF_SHIFT
config CGROUPS
bool "Control Group support"
help
- This option will let you use process cgroup subsystems
- such as Cpusets
+ 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".
- Say N if unsure.
+ When enabled, a new filesystem type "cgroup" is available
+ and can be mounted to control cpusets.
+
+ See <file:Documentation/cgroups.txt> for more information.
+
+ If unsure, say N.
config CGROUP_DEBUG
bool "Example debug cgroup subsystem"
@@ -300,9 +306,9 @@ config CGROUP_DEBUG
help
This option enables a simple cgroup subsystem that
exports useful debugging information about the cgroups
- framework
+ framework.
- Say N if unsure
+ If unsure, say N.
config CGROUP_NS
bool "Namespace cgroup subsystem"
@@ -317,19 +323,24 @@ config CPUSETS
bool "Cpuset support"
depends on SMP && CGROUPS
help
- This option will let you create and manage CPUSETs which
+ This option will let you create and manage "cpusets" which
allow dynamically partitioning a system into sets of CPUs and
Memory Nodes and assigning tasks to run only within those sets.
+
This is primarily useful on large SMP or NUMA systems.
- Say N if unsure.
+ See <file:Documentation/cpusets.txt> for more information.
+
+ If unsure, say N.
config FAIR_GROUP_SCHED
bool "Fair group CPU scheduler"
default y
help
- This feature lets CPU scheduler recognize task groups and control CPU
- bandwidth allocation to such task groups.
+ This feature enables the CPU scheduler to recognize task groups
+ and control CPU bandwidth allocation to such task groups.
+
+ See <file:Documentation/sched-design-CFS.txt> for more information.
choice
depends on FAIR_GROUP_SCHED
@@ -348,9 +359,10 @@ config FAIR_CGROUP_SCHED
help
This option allows you to create arbitrary task groups
using the "cgroup" pseudo filesystem and control
- the cpu bandwidth allocated to each such task group.
- Refer to Documentation/cgroups.txt for more information
- on "cgroup" pseudo filesystem.
+ the CPU bandwidth allocated to each such task group.
+
+ See <file:Documentation/cgroups.txt> for more information
+ on the "cgroup" pseudo filesystem.
endchoice
@@ -359,7 +371,7 @@ config CGROUP_CPUACCT
depends on CGROUPS
help
Provides a simple Resource Controller for monitoring the
- total CPU consumed by the tasks in a cgroup
+ total CPU consumed by the tasks in a cgroup.
config SYSFS_DEPRECATED
bool "Create deprecated sysfs files"
@@ -369,6 +381,7 @@ config SYSFS_DEPRECATED
"device"-link, the <subsystem>:<name>-link, and the
"bus"-link. It may also add deprecated key in the
uevent environment.
+
None of these features or values should be used today, as
they export driver core implementation details to userspace
or export properties which can't be kept stable across kernel
@@ -381,10 +394,20 @@ config SYSFS_DEPRECATED
If you are using a distro that was released in 2006 or later,
it should be safe to say N here.
+ If unsure, say N.
+
config PROC_PID_CPUSET
bool "Include legacy /proc/<pid>/cpuset file"
depends on CPUSETS
default y
+ help
+ This option provides the legacy /proc/<pid>/cpuset file.
+
+ It has been deprecated in favour of an additional line
+ in /proc/<pid>/status showing on which CPUs a process
+ may be scheduled.
+
+ If unsure, say Y.
config RELAY
bool "Kernel->user space relay support (formerly relayfs)"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
