From: Patrick B. <pb...@cs...> - 2008-09-24 12:33:41
|
BTW Paul, You could always rebuild you Gentoo kernel with the kernel_hz option set to 1000 as well, which will guarantee the timeouts (in the worst-case --when the device doesn't respond right away) will become 4 times shorter than the standard 250 Hz kernel. I think that'll help diagnose exactly which drivers should be reexamined for better timeout code. Dynamic ticks can achieve 1000Hz, but might only run 250Hz under light loads or when the laptop is running on battery -- I *think* it using heuristics similar to cpu frequency scaling. Paul Osmialowski wrote: > > On Wed, 24 Sep 2008, Fred Labrosse wrote: > >> Surely there must be better to do than loop waiting for the right amount of >> time to have elapsed. This makes the thread do some processing for nothing, >> therefore not freeing any processing time for anything else. > You can always put some little sleep call inside that loop so it won't be > busy looping all the time. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |