Am Donnerstag, 20. Mai 2004 06:52 schrieb Dave Airlie:
> It has been pointed out to me by Andrew and Fernando Pablo Lopez-Lezcano
> that we do a lot of sleeping in code that probably should reschedule
> rather than sleep,radeon_do_wait_for_idle being a prime example, this has
> a DRM_UDELAY(1), this messes up audio latencys,
>
> Now I'm not sure that wholesale replacing these with a conditional
> schedule is correct, but in most cases it looks like there should be no
> issues doing this, theses functions are all usually called from a process
> context,
Have a look into the DRI archive.
I played around with this two (2) years, ago when pre-emption was "developed"
as patch for 2.4. Do we need some "lock breaks" like Robert Love did?
Look for latencytest0.42-png benchmark.
Latest runs on SMP only show BAD X/DRI/DRM numbers with 2.6.
> My main worry is what to do on BSD about this?, should I just define a
> DRM_SCHED( delay ) and on Linux do a schedule and do a delay on BSD until
> someone steps up to figure it out?
>
>
> The r128/mga and i810 also suffer from something like this ..
Try latencytest0.42-png
Greetings,
Dieter
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
