X-Git-Url: http://git.osdn.net/view?p=linuxjm%2FLDP_man-pages.git;a=blobdiff_plain;f=original%2Fman7%2Fcpuset.7;h=407dc05ae2eae8afa18546cd58288b554117325b;hp=4a066cc2ff8213f70ba31541121c5406120c0428;hb=504d22d4a96ccb4837812eca7e370714a5ed57f3;hpb=8ac4ae9402fcb6247875731019a8371e0e9554a5

diff --git a/original/man7/cpuset.7 b/original/man7/cpuset.7
index 4a066cc2..407dc05a 100644
--- a/original/man7/cpuset.7
+++ b/original/man7/cpuset.7
@@ -72,7 +72,7 @@ The directories and files representing cpusets have normal
 file-system permissions.
 .PP
 Every process in the system belongs to exactly one cpuset.
-A process is confined to only run on the CPUs in
+A process is confined to run only on the CPUs in
 the cpuset it belongs to, and to allocate memory only
 on the memory nodes in that cpuset.
 When a process
@@ -292,7 +292,7 @@ section, below.
 .TP
 .IR cpuset.memory_pressure_enabled " (since Linux 2.6.16)"
 Flag (0 or 1).
-This file is only present in the root cpuset, normally
+This file is present only in the root cpuset, normally
 .IR /dev/cpuset .
 If set (1), the
 .I memory_pressure
@@ -788,13 +788,13 @@ balancing off the software clock described in
 .IR time (7).
 The setting of
 .I sched_relax_domain_level
-only applies to immediate load balancing.
+applies only to immediate load balancing.
 Regardless of the
 .I sched_relax_domain_level
 setting, periodic load balancing is attempted over all CPUs
 (unless disabled by turning off
 .IR sched_load_balance .)
-In any case, of course, tasks will only be scheduled to run on
+In any case, of course, tasks will be scheduled to run only on
 CPUs allowed by their cpuset, as modified by
 .BR sched_setaffinity (2)
 system calls.
@@ -841,7 +841,7 @@ The
 .I sched_relax_domain_level
 value of zero (0) always means
 don't perform immediate load balancing,
-hence that load balancing is only done periodically,
+hence that load balancing is done only periodically,
 not immediately when a CPU becomes available or another task becomes
 runnable.
 .PP
@@ -928,13 +928,13 @@ The following rules apply to each cpuset:
 Its CPUs and memory nodes must be a (possibly equal)
 subset of its parent's.
 .IP *
-It can only be marked
+It can be marked
 .IR cpu_exclusive
-if its parent is.
+only if its parent is.
 .IP *
-It can only be marked
+It can be marked
 .IR mem_exclusive
-if its parent is.
+only if its parent is.
 .IP *
 If it is
 .IR cpu_exclusive ,
@@ -1075,7 +1075,7 @@ there as well.
 In general, the kernel prefers to violate cpuset placement,
 rather than starving a process that has had all its allowed CPUs or
 memory nodes taken offline.
-User code should reconfigure cpusets to only refer to online CPUs
+User code should reconfigure cpusets to refer only to online CPUs
 and memory nodes when using hot-plug to add or remove such resources.
 .PP
 A few kernel-critical, internal memory-allocation requests, marked