On Nov 1, 2005, at 16:44:42, Bill Davidsen wrote:
Go back and reread the thread in the archives. The short answer is
that he who controls the code controls the decisions. I just fix it
everywhere, since 250 is too fast for optimal battery life, too
slow for optimal response or multimedia, and not optimal for any
server application I run (usenet, dns, mail, http, firewall).
A perfect compromise is one which makes everyone reasonably happy;
this is like the XOR of that, it leaves everyone slightly
dissatisfied. ;-)
I'm convinced that Linus choose this value to make everyone
slightly unhappy, so development of various variable rate and tick
skipping projects would continue. Unfortunately that doesn't seem
to have happened :-(
No, I think it's been happening, it's just that said developers are
still fixing the copious bugs in the various kernel concepts of
"time". IIRC John Stultz' rework is approaching completion, and when
that goes in it makes life a lot easier for the various dyntick and
variable tick projects.
Cheers,
Kyle Moffett
--
Unix was not designed to stop people from doing stupid things,
because that would also stop them from doing clever things.
-- Doug Gwyn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
