Hi Loic, On Mon, Nov 17, 2008 at 2:22 PM, Loic Domaigne <tech@xxxxxxxxxxxx> wrote: > Hi Michael, > > I've only a minor comment left. > > I've set the following reminder: > > <reminder> > > - effect of sched_setscheduler() on MT-process. Will follow up shortly. > - priority adjustment => later, when dealing with the topic on prio > inheritance/ceiling. There remains the FIXME in the page source. > </reminder> > > Cheers, > Loïc. > -- > >>>> .PP >>>> .BR pthread_setschedparam () >>>> may additionally fail with the following errors: >>>> .TP >>>> .B EINVAL >>>> .I policy >>>> is not a recognized policy, or >>>> .I param >>>> does not make sense for the >>>> .IR policy . >>> >>> I got troubled by the "may additionally", as "may" has a particular >>> meaning >>> in POSIX.1... >>> >>> But I guess, you just want to express that pthread_setschedparam() shall >>> fail if the policy or the param is invalid, right? >> >> Yes. > > What about using "pthread_setschedparam() can additionally [...]" in a > similar fashion to pthread_setcancelstate(3)" ? Done. Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
