Keith Whitwell wrote:
Michel Dänzer wrote:
The bottom line is that with a 2.5 kernel, sched_yield() will discard the time slice of the process, so misuse of it will cause bad performance.
I guess it's possible that this could be a problem. The yield is there to allow two graphics apps to somewhat smoothly share the card & cpu - otherwise you get very non-smooth interleaving or even starvation of some of the graphics apps on 2.4.
Wouldn't a better sollution be to release the hardware lock then re-get it? That should allow a blocked 3D process to get the lock and make progress. Or am I missing something about the way locking works in DRI?
The lock doesn't seem to be 'fair' like that - in practise it isn't transfered to the waiting process (unless you do a sched_yield() after unlocking).
Keith
------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
