aboutsummaryrefslogtreecommitdiffstats
path: root/man7/sched.7
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-11-24 22:17:17 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-11-29 21:50:15 +0100
commit45922aa8d355c73bba4ad0cae7b3b3e32663a31a (patch)
treece71c499087b599da977a419d4cf869c17917ad1 /man7/sched.7
parentee1f3c18a2ce4cee4abfbff7c20e6a102ade81c1 (diff)
downloadman-pages-45922aa8d355c73bba4ad0cae7b3b3e32663a31a.tar.gz
sched.7: srcfix: add details to FIXME
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/sched.7')
-rw-r--r--man7/sched.79
1 files changed, 9 insertions, 0 deletions
diff --git a/man7/sched.7 b/man7/sched.7
index 4787d752f7..a72fcaa9be 100644
--- a/man7/sched.7
+++ b/man7/sched.7
@@ -766,6 +766,15 @@ and the setting has the same effect as modifying the nice level via
.\"
.\" FIXME How do the nice value of a process and the nice value of
.\" an autogroup interact? Which has priority?
+.\"
+.\" It *appears* that the autogroup nice value is used for CPU distribution
+.\" between task groups, and that the process nice value has no effect there.
+.\" (I.e., suppose two autogroups each contain a CPU-bound process,
+.\" with one process having nice==0 and the other having nice==19.
+.\" It appears that they each get 50% of the CPU.)
+.\" It appears that the process nice value has effect only with respect to
+.\" scheduling relative to other processes in the *same* autogroup.
+.\" Is this correct?
The use of the
.BR cgroups (7)