From daf627c88f02a8eece42490079c2b983cec3a289 Mon Sep 17 00:00:00 2001 From: Chris Metcalf Date: Tue, 9 Aug 2016 11:31:41 +0200 Subject: [PATCH] taskset: clarify that masks are always hex in man page The man page confusingly says that the mask is "typically" hexadecimal, when in fact it is always hexadecimal. Fix the language, and provide an additional example with no leading "0x". Also, provide an example using the --cpu-list option. Signed-off-by: Chris Metcalf Signed-off-by: Karel Zak --- schedutils/taskset.1 | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/schedutils/taskset.1 b/schedutils/taskset.1 index 901f9faf5f..3ea03b7e25 100644 --- a/schedutils/taskset.1 +++ b/schedutils/taskset.1 @@ -51,7 +51,10 @@ to the last logical CPU. Not all CPUs may exist on a given system but a mask may specify more CPUs than are present. A retrieved mask will reflect only the bits that correspond to CPUs physically on the system. If an invalid mask is given (i.e., one that corresponds to no valid CPUs on the current system) an -error is returned. The masks are typically given in hexadecimal. For example, +error is returned. The masks may be specified in hexadecimal (with or without +a leading "0x"), or as a cpu list with the +.BR \-\-cpu\-list +option. For example, .RS 4 .TP 12 .BR 0x00000001 @@ -61,7 +64,13 @@ is processor #0, is processors #0 and #1, .TP .BR 0xFFFFFFFF -is all processors (#0 through #31). +is processors #0 through #31, +.TP +.BR 32 +is processors #1, #4, and #5, +.TP +.BR \-\-cpu\-list\ 0-2,6 +is processors #0, #1, #2, and #6. .RE .PP When -- 2.47.2