Hi all,
Quoting “http://www.codemonkey.org.uk/post-halloween-2.5.txt”, section
"Process scheduler improvements":
<<
The behavior of sched_yield() changed a lot. A task that uses
this system call should now expect to sleep for possibly a very
long time. Tasks that do not really desire to give up the
processor for a while should probably not make heavy use of this
function. Unfortunately, some GUI programs (like Open Office)
do make excessive use of this call and under load their
performance is poor. It seems this new 2.5 behavior is optimal
but some user-space applications may need fixing.
Some games coded with SDL uses sched_yield() through SDL_Delay(0) in passive
wait loops. The granularity in the current linux kernel is 10ms, and a lot
of games rely on this. Running them on future kernel may lead to slowdowns
and others misbehaviours.
I think everybody’s common practice may change from passive wait loops
(while(waiting) SDL_wait(); ) to active wait loops (while(waiting) ; ),
provided this can put the whole system under heavy load on older (and the
current) kernels.
Best Regards,
^IoDream^_____________________________________________________________________
Envie de discuter en “live” avec vos amis ? T?l?charger MSN Messenger
http://www.ifrance.com/_reloc/m la 1?re messagerie instantan?e de France