Cool! That means movies don't need to run faster than 5
frames/second. Maybe 10 frames/second for plenty of overkill. No
need to look at keyboard and mice any more frequently either, what a
relief. (Any why do silly gamers want to go so much higher?)
Sarcasm mode "off" now...just because some experiments show it takes
humans a long time to push the correct button when you show them a
picture of a banana doesn't mean there is no reason to have a user
interface do anything any faster. (I can come up with plenty of
examples if you would like.)
OK, now that I have pissed off a big hunk of the folks on the list,
let me bring up a different question:
How does all this fit into doing a tick-less kernel?
There is something appealing about doing stuff only when there is
stuff to do, like: respond to input, handle some device that becomes
ready, or let another process run for a while. Didn't IBM do some
nice work on this for Linux? (*Was* it nice work?) I was under the
impression that the current kernel isn't that far from being tickless.
A tickless kernel would be wonderful for battery powered devices that
could literally shut off when there be nothing to do, and it seems it
would (trivially?) help performance on high end power hogs too.
Why do we have regular HZ ticks? (Other than I think I remember Linus
saying that he likes them.)
Thanks,
-kb, the Kent who knows more about user interfaces than he does
preemption.
-
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/