4 ms·
> Tanenbaum was right Citation needed. Where do you get that? Performance-wise the biggest problem of OS X is still that part that is based on the "many server
by acqq 16y ago
> Tanenbaum was right
Citation needed. Where do you get that? Performance-wise the biggest problem of OS X is still that part that is based on the "many servers are the OS" idea.
That's the reason why this exists:
http://www.ertos.nicta.com.au/software/darbat/ http://www.ertos.nicta.com.au/software/darbat/
Also, NT wanted to try moving in that direction but the critical parts are not "many servers."
Also, there's a reason why L4 was developed (note: post Tanenbaum): the "real" microkernels were very problematic performance-wise and it's actually harder to produce them (example: Gnu Hurd)
http://en.wikipedia.org/wiki/L4_microkernel_family http://en.wikipedia.org/wiki/L4_microkernel_family
http://en.wikipedia.org/wiki/GNU_Hurd http://en.wikipedia.org/wiki/GNU_Hurd
- eru 16y agoOn the other hand, you can view the current fad of virtualized everything and hypervisors as a kind of exokernel.
- acqq 16y ago> you can view the current fad of virtualized everything and hypervisors as a kind of exokernel. No I can't, as long as the underlying OS is still a monolithic one, thus selected because it's the fastest and the most convenient to be maintained.
- eru 16y agoNot all hypervisors have an underlying OS. I should expressed myself more clearly. I was talking about bare metal hypervisors, not hosted hypervisors. (See http://en.wikipedia.org/wiki/Hypervisor#Classification http://en.wikipedia.org/wiki/Hypervisor#Classification) We have some experiments with very stripped down domains (i.e. virtual machines) that make full use of paravirtualization. They are quite close to being processes in an exokernel OS. And boot up really fast---like processes should do.
- acqq 16y agoThanks, my wording was indeed clumsy, but it doesn't change the fact: the hypervisor is simply not doing the stuff that the classical OS kernel does, it's not replacing anything, it's just a layer with some specific new functionality, so when you're changing the meaning of the terms being discussed of course it can appear that you're winning the argument, whereas you're just performing tricks. No matter from which direction you observe the systems, the overall functionality possible with monolithic kernels is still not really substituted with something better.
- eru 16y ago> the hypervisor is simply not doing the stuff that the classical OS kernel does And that makes the comparison with exokernels apt. Exokernels are not supposed to do what normal kernels do. (Though if you run a normal kernel on top of a hypervisor or exokernel, in a sense you haven't reached the true potential of the system and your critique is more than valid.)