LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

cpuset.7: Minor wording fixes 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Nicolas Franois 2009-09-28 12:08:54 +02:00 committed by Michael Kerrisk
parent e46256a48c
commit 4d1de263eb
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
man7/cpuset.7
View File

@ -254,8 +254,8 @@ Regardless of the
.I mem_exclusive
setting, if one cpuset is the ancestor of another,
then their memory nodes must overlap, because the memory
nodes of any cpuset are always a subset of that cpuset's
parent cpuset.
nodes of any cpuset are always a subset of the memory nodes
of that cpuset's parent cpuset.
.\" ==================== mem_hardwall ====================
.TP
.IR mem_hardwall " (since Linux 2.6.26)"
@ -620,14 +620,14 @@ of their parent.
Setting memory spreading causes allocations for the affected page or
slab caches to ignore the process's NUMA memory policy and be spread
instead.
However, the affect of these changes in memory placement
However, the effect of these changes in memory placement
caused by cpuset-specified memory spreading is hidden from the
.BR mbind (2)
or
.BR set_mempolicy (2)
calls.
These two NUMA memory policy calls always appear to behave as if
no cpuset-specified memory spreading is in affect, even if it is.
no cpuset-specified memory spreading is in effect, even if it is.
If cpuset memory spreading is subsequently turned off, the NUMA
memory policy most recently specified by these calls is automatically
re-applied.
@ -755,7 +755,7 @@ So, for example, if the top cpuset has the flag
enabled, then the scheduler will load balance across all
CPUs, and the setting of the
.I sched_load_balance
flag in other cpusets has no affect,
flag in other cpusets has no effect,
as we're already fully load balancing.
.PP
Therefore in the above two situations, the flag
@ -1359,7 +1359,7 @@ set to
.BR EACCES ,
and the creation and truncation options on
.BR open (2)
have no affect.
have no effect.
.\" ================== EXAMPLE ==================
.SH EXAMPLE
The following examples demonstrate querying and setting cpuset
@ -1470,11 +1470,11 @@ only one process PID at a time may be written to the
.I tasks
file.
.PP
The same affect (writing one PID at a time) as the
The same effect (writing one PID at a time) as the
.I while
loop can be accomplished more efficiently, in fewer keystrokes and in
syntax that works on any shell, but alas more obscurely, by using the
.I \-u
.B \-u
(unbuffered) option of
.BR sed (1):
.in +4n