Post a Comment
Linux was still light and efficient software at this stage, despite its very alpha stability and functionality -- not even 2500 lines. (I didn't know that it had jumped from 0.03 to 0.10 though -- I thought that 0.04 through 0.09 were just lost as trivialia or something.)
Hmm. Gives me the idea for a crazy project...
Auto-dialing a *hard drive*? That is a goof of epic proportions -- and apparently, if it stirred him to develop Linux, it was the kind of goofs epics are made of.
This is a pretty good algorithm, all things considered. Remember, Linux won't support SMP for another four years. Traversing the task list 2-4 times isn't great, but O(N) is perfectly acceptable for dozens of tasks. Some commercial UNIX schedulers still scale linearly.
They also still use the "C = C/2 + P" function to give sleepers a bounded priority boost over hogs. Maverick sysadmins can tune the denominator these days, but the theory is identical. Yes, the algorithm is non-deterministic fuzzy math, but it's simple and it works.
see http://www.manlug.org/content/blogsection/5/71/ for qemu images of mcc linux.
Design is evolutionary and synchronous with the hardware and functional loads of the time.And remember, that Linux wasn't started to create an enterprise operating system. That sort of happened by accident.
Originally, it was a kernel to run on cheap x86 hardware.
People's learning is also evolutionary. Finally, point me out to any place where I can check on your ability to write a kernel at the same age when Linus started Linux.





