This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: pthread_attr_setsched behaviour
- From: Manuel Traut <manut at linutronix dot de>
- To: "Michael Kerrisk (man-pages)" <mtk dot manpages at gmail dot com>
- Cc: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, Siddhesh Poyarekar <siddhesh at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Rich Felker <dalias at aerifal dot cx>
- Date: Thu, 18 Apr 2013 16:58:57 +0200
- Subject: Re: pthread_attr_setsched behaviour
- References: <20130416133211 dot GB15869 at linutronix dot de> <20130417124952 dot GF10160 at spoyarek dot pnq dot redhat dot com> <CAAHN_R263JNgUMezfbtu-i_PT9Cd=rpqXWCgRdK=BdPVDxRZbQ at mail dot gmail dot com> <CAKgNAkirTJrjTUVGSgrRxR8iO_+PV+7c0nGx5kFD51_r1cUZMg at mail dot gmail dot com> <20130418104646 dot GF15869 at linutronix dot de> <CAKgNAkhAQpv2vz81LmNOH=u=pD_JtNr2YioFvBpScsGGzZegsw at mail dot gmail dot com>
On 13:41 Thu 18 Apr , Michael Kerrisk (man-pages) wrote:
> >> >> This is the best option currently. I've added Michael Kerrisk to cc;
> >> >> he maintains the man pages.
> >>
> >> I have applied the patch below.
> >
> > IMHO, the additional information would also apply for pthread_attr_setscope
>
> Manuel -- opinion is not enough ;-). Can you please tell me what facts
> lead you to have the opinion?
because, man 3p pthread_attr_setinheritsched says:
...
The following thread scheduling attributes defined by
IEEE Std 1003.1-2001 are affected by the inheritsched attribute: sched-
uling policy ( schedpolicy), scheduling parameters ( schedparam), and
scheduling contention scope ( contentionscope).
...
But only one scheduling scope (PTHREAD_SCOPE_SYSTEM) is supported in glibc.
So pthread_attr_setscope has currently no effect.
So it doesn't change anything if you call pthread_attr_setinheritsched or not
(at least at the moment). :-)
Thanks,
Manuel