getpriority.2: Enhance discussion of kernel nice range versus user-space nice range

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-05-16 08:29:59 +02:00
parent 0ebe771f91
commit 8d0641ea0a
1 changed files with 3 additions and 1 deletions

View File

@ -212,7 +212,7 @@ defined in
.\"
.SS C library/kernel ABI differences
Within the kernel, nice values are actually represented
using the corresponding range 40..1
using the range 40..1
(since negative numbers are error codes) and these are the values
employed by the
.BR setpriority ()
@ -223,6 +223,8 @@ The glibc wrapper functions for these system calls handle the
translations between the user-land and kernel representations
of the nice value according to the formula
.IR "unice\ =\ 20\ \-\ knice" .
(Thus, the kernels 40..1 range corresponds to the
range \-20..19 as seen by user space.)
.SH BUGS
According to POSIX, the nice value is a per-process setting.
However, under the current Linux/NPTL implementation of POSIX threads,