sched.7: Minor rewording of discussion of nice value

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2016-11-28 07:06:59 +01:00
parent 31046c3cbd
commit bcbb240cf4
1 changed files with 7 additions and 6 deletions

View File

@ -388,24 +388,25 @@ but denied to run by the scheduler.
This ensures fair progress among all \fBSCHED_OTHER\fP threads.
.\"
.SS The nice value
The nice value is a per-process attribute
The nice value is an attribute
that can be used to influence the CPU scheduler to
favor or disfavor a process in scheduling decisions.
It affects the scheduling of
.BR SCHED_OTHER
and
.BR SCHED_BATCH
(see below)
processes.
According to POSIX.1, the threads in a process should share a nice value.
However, on Linux, the nice value is a per-thread attribute:
different threads in the same process may have different nice values.
(see below) processes.
The nice value can be modified using
.BR nice (2),
.BR setpriority (2),
or
.BR sched_setattr (2).
According to POSIX.1, the nice value is a per-process attribute;
that is, the threads in a process should share a nice value.
However, on Linux, the nice value is a per-thread attribute:
different threads in the same process may have different nice values.
The range of the nice value
varies across UNIX systems.
On modern Linux, the range is \-20 (high priority) to +19 (low priority).