From: Michael Kerrisk Date: Sat, 10 Dec 2016 09:34:46 +0000 (+0100) Subject: sched_setscheduler.2: Mention SCHED_DEADLINE X-Git-Tag: man-pages-4.09~54 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=16109ab35428bb74be188fed6a08e5de1b3721a9;p=thirdparty%2Fman-pages.git sched_setscheduler.2: Mention SCHED_DEADLINE Give the reader a clue that there is another policy() available that can't be set via sched_setscheduler(2). See https://bugzilla.redhat.com/show_bug.cgi?id=1390546 Reported-by: Daniel Berrange Signed-off-by: Michael Kerrisk --- diff --git a/man2/sched_setscheduler.2 b/man2/sched_setscheduler.2 index bf87fc4230..1bb5b56548 100644 --- a/man2/sched_setscheduler.2 +++ b/man2/sched_setscheduler.2 @@ -171,8 +171,13 @@ POSIX.1-2001, POSIX.1-2008 (but see BUGS below). The \fBSCHED_BATCH\fP and \fBSCHED_IDLE\fP policies are Linux-specific. .SH NOTES Further details of the semantics of all of the above "normal" -and "real-time" scheduling policies can be found in -.BR sched (7). +and "real-time" scheduling policies can be found in the +.BR sched (7) +manual page. +That page also describes an additional policy, +.BR SCHED_DEADLINE , +which is settable only via +.BR sched_setattr (2). POSIX systems on which .BR sched_setscheduler ()