Re: For review: pthread_setschedparam.3

[Loic Domaigne <tech-Z4JMKDdsf89Wk0Htik3J/w@public.gmane.org>]

Hi Michael,

I've only a minor comment left.

I've set the following reminder:

<reminder>

- effect of sched_setscheduler() on MT-process.
- priority adjustment => later, when dealing with the topic on prio 
inheritance/ceiling.

</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)" ?
--
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