From 76eac093e3b512659baa51ba77b781ed4e24f668 Mon Sep 17 00:00:00 2001 From: Yuri Kozlov Date: Sat, 21 Jun 2014 09:16:01 +0400 Subject: [PATCH] cpuset.7: tfix Signed-off-by: Michael Kerrisk --- man7/cpuset.7 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man7/cpuset.7 b/man7/cpuset.7 index 3c74dac18..1b89d7960 100644 --- a/man7/cpuset.7 +++ b/man7/cpuset.7 @@ -247,7 +247,7 @@ format of Flag (0 or 1). If set (1), the cpuset has exclusive use of its memory nodes (no sibling or cousin may overlap). -Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below.) +Also if set (1), the cpuset is a \fBHardwall\fR cpuset (see below). By default this is off (0). Newly created cpusets also initially default this to off (0). @@ -261,7 +261,7 @@ of that cpuset's parent cpuset. .TP .IR cpuset.mem_hardwall " (since Linux 2.6.26)" Flag (0 or 1). -If set (1), the cpuset is a \fBHardwall\fR cpuset (see below.) +If set (1), the cpuset is a \fBHardwall\fR cpuset (see below). Unlike \fBmem_exclusive\fR, there is no constraint on whether cpusets marked \fBmem_hardwall\fR may have overlapping