ソースを参照

cgroups: Documentation: fix trivial typos and wrong paragraph numberings

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Tejun Heo <tj@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
SeongJae Park 10 年 前
コミット
29d293b600
2 ファイル変更7 行追加7 行削除
  1. 3 3
      Documentation/cgroups/cpusets.txt
  2. 4 4
      Documentation/cgroups/memory.txt

+ 3 - 3
Documentation/cgroups/cpusets.txt

@@ -445,7 +445,7 @@ across partially overlapping sets of CPUs would risk unstable dynamics
 that would be beyond our understanding.  So if each of two partially
 that would be beyond our understanding.  So if each of two partially
 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
 overlapping cpusets enables the flag 'cpuset.sched_load_balance', then we
 form a single sched domain that is a superset of both.  We won't move
 form a single sched domain that is a superset of both.  We won't move
-a task to a CPU outside it cpuset, but the scheduler load balancing
+a task to a CPU outside its cpuset, but the scheduler load balancing
 code might waste some compute cycles considering that possibility.
 code might waste some compute cycles considering that possibility.
 
 
 This mismatch is why there is not a simple one-to-one relation
 This mismatch is why there is not a simple one-to-one relation
@@ -552,8 +552,8 @@ otherwise initial value -1 that indicates the cpuset has no request.
    1  : search siblings (hyperthreads in a core).
    1  : search siblings (hyperthreads in a core).
    2  : search cores in a package.
    2  : search cores in a package.
    3  : search cpus in a node [= system wide on non-NUMA system]
    3  : search cpus in a node [= system wide on non-NUMA system]
- ( 4  : search nodes in a chunk of node [on NUMA system] )
- ( 5  : search system wide [on NUMA system] )
+   4  : search nodes in a chunk of node [on NUMA system]
+   5  : search system wide [on NUMA system]
 
 
 The system default is architecture dependent.  The system default
 The system default is architecture dependent.  The system default
 can be changed using the relax_domain_level= boot parameter.
 can be changed using the relax_domain_level= boot parameter.

+ 4 - 4
Documentation/cgroups/memory.txt

@@ -326,7 +326,7 @@ per cgroup, instead of globally.
 
 
 * tcp memory pressure: sockets memory pressure for the tcp protocol.
 * tcp memory pressure: sockets memory pressure for the tcp protocol.
 
 
-2.7.3 Common use cases
+2.7.2 Common use cases
 
 
 Because the "kmem" counter is fed to the main user counter, kernel memory can
 Because the "kmem" counter is fed to the main user counter, kernel memory can
 never be limited completely independently of user memory. Say "U" is the user
 never be limited completely independently of user memory. Say "U" is the user
@@ -354,19 +354,19 @@ set:
 
 
 3. User Interface
 3. User Interface
 
 
-0. Configuration
+3.0. Configuration
 
 
 a. Enable CONFIG_CGROUPS
 a. Enable CONFIG_CGROUPS
 b. Enable CONFIG_MEMCG
 b. Enable CONFIG_MEMCG
 c. Enable CONFIG_MEMCG_SWAP (to use swap extension)
 c. Enable CONFIG_MEMCG_SWAP (to use swap extension)
 d. Enable CONFIG_MEMCG_KMEM (to use kmem extension)
 d. Enable CONFIG_MEMCG_KMEM (to use kmem extension)
 
 
-1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?)
+3.1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?)
 # mount -t tmpfs none /sys/fs/cgroup
 # mount -t tmpfs none /sys/fs/cgroup
 # mkdir /sys/fs/cgroup/memory
 # mkdir /sys/fs/cgroup/memory
 # mount -t cgroup none /sys/fs/cgroup/memory -o memory
 # mount -t cgroup none /sys/fs/cgroup/memory -o memory
 
 
-2. Make the new group and move bash into it
+3.2. Make the new group and move bash into it
 # mkdir /sys/fs/cgroup/memory/0
 # mkdir /sys/fs/cgroup/memory/0
 # echo $$ > /sys/fs/cgroup/memory/0/tasks
 # echo $$ > /sys/fs/cgroup/memory/0/tasks