[PATCH] cgroups: Documentation: fix trivial typos and wrong numberings

[SeongJae Park]

Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
  Documentation/cgroups/cpusets.txt | 6 +++---
  Documentation/cgroups/memory.txt  | 8 ++++----
  2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation/cgroups/cpusets.txt 
b/Documentation/cgroups/cpusets.txt
index 7740038..2e921b5 100644
--- a/Documentation/cgroups/cpusets.txt
+++ b/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
  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
-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.

  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).
     2  : search cores in a package.
     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
  can be changed using the relax_domain_level= boot parameter.
diff --git a/Documentation/cgroups/memory.txt 
b/Documentation/cgroups/memory.txt
index 02ab997..228c1cc 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -321,7 +321,7 @@ per cgroup, instead of globally.

  * 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
  never be limited completely independently of user memory. Say "U" is the 
user
@@ -349,7 +349,7 @@ set:

  3. User Interface

-0. Configuration
+3.0. Configuration

  a. Enable CONFIG_CGROUPS
  b. Enable CONFIG_RESOURCE_COUNTERS
@@ -357,12 +357,12 @@ c. Enable CONFIG_MEMCG
  d. Enable CONFIG_MEMCG_SWAP (to use swap 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
  # mkdir /sys/fs/cgroup/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
  # echo $$ > /sys/fs/cgroup/memory/0/tasks

--
1.9.1


Thanks,
SeongJae Park

>
> Thanks,
>
> jon
>
--
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/