[PATCH 2.6.25-rc2 6/9] Kconfig: Improve init/Kconfig help descriptions - CGROUPS

From: Nick Andrew
Date: Thu Feb 21 2008 - 19:56:19 EST


Rewrite the help descriptions for clarity, accuracy and consistency.

Kernel config options affected:

- CGROUPS
- CGROUP_DEBUG
- CPUSETS
- GROUP_SCHED
- CGROUP_SCHED
- CGROUP_CPUACCT
- SYSFS_DEPRECATED
- CGROUP_MEM_CONT
- PROC_PID_CPUSET

Signed-off-by: Nick Andrew <nick@xxxxxxxxxxxxxxx>
---
Try #3.

--- a/init/Kconfig 2008-02-20 09:34:48.000000000 +1100
+++ b/init/Kconfig 2008-02-21 08:22:39.000000000 +1100
@@ -276,10 +276,17 @@ 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 enable processes to be grouped into "cgroups"
+ to facilitate tracking and resource management. For example
+ a cgroup can tie a set of processes to a set of CPUs using
+ "cpusets".

- Say N if unsure.
+ See <file:Documentation/cgroups.txt> for more information.
+
+ If you say Y here, you probably want to enable one or
+ more of the cgroup subsystem options below.
+
+ If unsure, say N.

config CGROUP_DEBUG
bool "Example debug cgroup subsystem"
@@ -287,9 +294,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"
@@ -304,19 +311,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 GROUP_SCHED
bool "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.

config FAIR_GROUP_SCHED
bool "Group scheduling for SCHED_OTHER"
@@ -346,9 +358,10 @@ config 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

@@ -357,7 +370,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 RESOURCE_COUNTERS
bool "Resource counters"
@@ -375,6 +388,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
@@ -394,10 +408,20 @@ config CGROUP_MEM_CONT
Provides a memory controller that manages both page cache and
RSS memory.

+ 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 /proc/<pid>/cpuset file.
+
+ This file contains the name of the cpuset in which
+ the process is executing. For more information, see
+ <file:Documentation/cpusets.txt>
+
+ 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/