pthread_attr_setschedparam.3, pthread_setschedparam.3: Remove text saying that only sched_priority is required by POSIX.1

Loic Domaigne points out that if a system implements
SCHED_SPORADIC (which Linux does not), then other
fields are also specified in sched_param.  The simple
solution is just to remove that phrase from the man
page.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Reported-by: Loic Domaigne <tech@domaigne.com>
This commit is contained in:
Michael Kerrisk 2008-11-17 12:41:16 -05:00
parent 65cc854059
commit 4c5f54136d
2 changed files with 4 additions and 6 deletions

View File

@ -21,7 +21,7 @@
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.TH PTHREAD_ATTR_SETSCHEDPARAM 3 2008-11-06 "Linux" "Linux Programmer's Manual"
.TH PTHREAD_ATTR_SETSCHEDPARAM 3 2008-11-17 "Linux" "Linux Programmer's Manual"
.SH NAME
pthread_attr_setschedparam, pthread_attr_getschedparam \- set/get
scheduling parameter attributes in thread attributes object
@ -64,8 +64,7 @@ struct sched_param {
.fi
.in
As can be seen, only one scheduling parameter is supported
(this is the only parameter specified by POSIX.1-2001).
As can be seen, only one scheduling parameter is supported.
For details of the permitted ranges for scheduling priorities
in each scheduling policy, see
.BR sched_setscheduler (2).

View File

@ -21,7 +21,7 @@
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.TH PTHREAD_SETSCHEDPARAM 3 2008-11-11 "Linux" "Linux Programmer's Manual"
.TH PTHREAD_SETSCHEDPARAM 3 2008-11-17 "Linux" "Linux Programmer's Manual"
.SH NAME
pthread_setschedparam, pthread_setschedparam \- set/get
scheduling policy and parameters of a thread
@ -66,8 +66,7 @@ struct sched_param {
.fi
.in
As can be seen, only one scheduling parameter is supported
(this is the only parameter specified by POSIX.1-2001).
As can be seen, only one scheduling parameter is supported.
For details of the permitted ranges for scheduling priorities
in each scheduling policy, see
.BR sched_setscheduler (2).