Pierre Peiffer a écrit :
Ulrich Drepper a écrit :
I have never seen performance numbers for this. If it is punishing
existing code in a measurable way I think it's not anacceptable default
behavior.
May be, supposing it makes sense to respect the priority order only for
real-time pthreads, I can register all SCHED_OTHER threads to the same
MAX_RT_PRIO priotity ?
Moreover, the performance must be considered, sure, but after all, "man
pthread_cond_broadcast" says:
<<
If more than one thread is blocked on a condition variable, the
scheduling policy shall determine the order in which threads are
unblocked.
>>
... this is not true today ...
(of course, "shall" does not mean "mandatory", I know ;-) )
--
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
