public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
To: Michael Kerrisk
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] sched_rr_get_interval.2: update Linux notes
Date: Tue, 11 Oct 2011 13:40:20 +0200	[thread overview]
Message-ID: <4E942B24.2080608@ladisch.de> (raw)

Signed-off-by: Clemens Ladisch <clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>

--- a/man2/sched_rr_get_interval.2
+++ b/man2/sched_rr_get_interval.2
@@ -98,18 +98,24 @@
 .\" 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.
+.\" It is again true for at least Linux 2.6.12, but stopped in 2.6.24.
 POSIX does not specify any mechanism for controlling the size of the
 round-robin time quantum.
 However, Linux provides a (nonportable) method of doing this.
-The quantum can be controlled by adjusting the process's nice value (see
+The quantum of both
+.B SCHED_RR
+and
+.B SCHED_OTHER
+processes can be controlled by adjusting the process's nice value (see
 .BR setpriority (2)).
 Assigning a negative (i.e., high) nice value results in a longer quantum;
 assigning a positive (i.e., low) nice value results in a shorter quantum.
 The default quantum is 0.1 seconds;
 the degree to which changing the nice value affects the
 quantum has varied somewhat across kernel versions.
+Since Linux 2.6.24, the
+.B SCHED_RR
+quantum cannot be modified.
 .\" .SH BUGS
 .\" As of Linux 1.3.81
 .\" .BR sched_rr_get_interval ()
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-10-11 11:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 11:40 Clemens Ladisch [this message]
     [not found] ` <4E942B24.2080608-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2011-10-11 14:52   ` [PATCH] sched_rr_get_interval.2: update Linux notes Michael Kerrisk
     [not found]     ` <CAKgNAkgq42JVZ0whV-13Qq=3QJNgbuApxJuLHeg4sUtkbexDMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-11 16:03       ` Clemens Ladisch
2011-10-16  5:08   ` Michael Kerrisk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E942B24.2080608@ladisch.de \
    --to=clemens-p6gi/4k7komelga04laivw@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox