Roland Scheidegger wrote:
(e.g. while (ret && (errno == EINTR || errno == EBUSY));)
And by looking at it, does it make sense that the timeout value in
the kernel depends on the kernel-of-the-day HZ value, rather than
some hardware-dependant (probably fixed) value?
Isn't the timeout value dependent on HZ?
3*HZ is always 3 seconds no matter what HZ is (provided its the same
value used to compile the kernel).
Ah right. I think I misinterpreted something. That said, 3 seconds
sounds like a rather long time, why would there still be timeouts?
Two reasons:
1) Badly configured hardware, the hardware does more than it has to
(driver optimization issue).
2) Give the hardware a computational task that takes more than 3 seconds
in this hardware (some benchmarks or maybe Doom 3 @ 1600x1200 :) ).
Not everyday situations, but exiting an app because the frame rate is
below 1/3 fps is not very helpful. Maybe print a warning when this happens.
Rune Petersen
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
