| | Subject | Re: -mm -> 2.6.13 merge status (HZ -> 250?) | | From | Alan Cox <> | | Date | Tue, 21 Jun 2005 19:09:04 +0100 |
| |
On Maw, 2005-06-21 at 17:26, Lee Revell wrote: > Consider a program with a 5ms RT constraint, like a game or mplayer. > Currently it uses the RTC on 2.4/HZ=100 systems and usleep() on > 2.6/HZ=1000. Allowing HZ to regress to 250 would force us to handle > 2.4, 2.6.1 - 2.6.12, and 2.6.13+ separately. It would be a huge mess.
Vendors already ship 100Hz and 1KHz kernels. 2.4 and 2.6 are different already. I can see the argument for not picking another new value though. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|