From 8d30cbf47800f775b3821be4f0c1eb60e3608c56 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Wed, 23 Apr 2008 09:10:40 +0000 Subject: [PATCH] Added some FIXMEs. --- man2/sched_rr_get_interval.2 | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/man2/sched_rr_get_interval.2 b/man2/sched_rr_get_interval.2 index ada5434b0..96a59eed2 100644 --- a/man2/sched_rr_get_interval.2 +++ b/man2/sched_rr_get_interval.2 @@ -56,7 +56,11 @@ into \fI*tp\fP. The identified process should be running under the .B SCHED_RR scheduling policy. - +.\" FIXME . On Linux, sched_rr_get_interval() +.\" returns the timeslice for SCHED_OTHER processes -- this timeslice +.\" is influenced by the nice value. +.\" For SCHED_FIFO processes, this always returns 0. +.\" .\" The round-robin time quantum value is not alterable under Linux .\" 1.3.81. .\" @@ -89,6 +93,13 @@ The process whose ID is \fIpid\fP could not be found. POSIX.1-2001. .SH NOTES .SS Linux Notes +.\" FIXME +.\" From at least Linux 2.6.9, the following is no longer true +.\" for SCHED_RR processes. For RR processes the timeslice is always +.\" DEF_TIMESLICE, or 0.1 secs. +.\" Was the following really true for older kernels? +.\" Must build a 2.6.8 kernel and retest, and rewrite the following text +.\" appropriately. POSIX does not specify any mechanism for controlling the size of the round-robin time quantum. However, Linux provides a (non-portable) method of doing this.