5 ms·
A friend of mine in this discussion (microkernel vs monolithic kernels) discussed it this way; "CPU architects design for monolithic kernels because they are t
by ChuckMcM 11y ago
A friend of mine in this discussion (microkernel vs monolithic kernels) discussed it this way;
"CPU architects design for monolithic kernels because they are the only type that have been commercially successful, further in the absence of any barrier to making a choice (micro/mono) the monolithic kernel choice has always prevailed. This may be a consipiracy on a monumental scale but it also may be that microkernels just don't work as well as their proponents would wish, and no amount of engineering investment has changed that in 20 years."
Ok, so that probably isn't word for word, but he said it in 2010, and here it is 2016 and its still true. I love the conceptual simplicity of micro kernels, they are easy to abstract and they are easier to show they have predictable response in a wide variety of situations. I have also met some really strong advocates for them, and listened as the QNX folks went on and on about how much they were investing in making these things better than any alternative, and yet here we are. I haven't attended a SOSP[1] symposium in a while but I do still look through their proceedings when I get a chance at the Stanford Library. And it hasn't felt like microkernels have really made any conceptual improvements in their design. Instead we are seeing more and more work going toward multiprocessing with a monolithic kernel on each processor and the thread separation being an interconnect rather than a memory bus.
[1] http://www.sosp.org http://www.sosp.org
- aidenn0 11y agoTFA specifically lists several successful commercial microkernels (disclaimer: I work for a company that makes one of the kernels listed). In addition, there are a lot of CPU features that are incredibly useful for microkernels that have been created both in embedded and non-embedded parts.
- shenberg 11y agoWhat's common to Symbian, QNX, car-infotainment and in-flight entertainment (system's I've interacted with)? In all those cases (QNX->blackberry) they're systems with awful input lag from my personal experience. I also noticed that performance was mentioned in the article only in terms of throughput. coincidence?
- hhw 11y agoYou have this backwards. QNX is a real-time operating system, and is optimized for response time vs Linux, which is a general purpose operating system typically optimized for throughput, although some work has been done on modifications to allow for real-time OS like scheduling.
- jschwartzi 11y agoIt's possible to write a UI on QNX that doesn't have awful input lag. Doing so requires you to write software that prioritizes the UI, and to create a UI that runs in short, deterministic bursts. I have some experience with this because that is exactly what I'm doing in my current job, and with QNX to boot.
- aidenn0 11y agoThat sounds interesting! A lot of UI libraries want bursts of CPU time that are longer than acceptable in many real time systems, despite the amortized cost being very low.
- derefr 11y ago> monolithic kernels ... are the only type that have been commercially successful Both Windows and OSX have (somewhat-compromised) microkernels at their core. As do the operating systems for most game consoles.
- ww520 11y agoWindows NT started as microkernel but Microsoft found out pretty early that the GUI performance was pretty bad so they had to push the GUI and other subsystems into the kernel. That pretty much killed the microkernel mantra.
- Sanddancer 11y agoThe past few versions have actually been swinging back to microkernel. Graphics drivers, for example, exist in user space, as well as audio drivers, etc.
- ChuckMcM 11y agoWatching this particular dance has been interesting. And the whole Wayland / X discussion as well. One of the more interesting thing about Graphics drivers has been that while it used to be the CPU that was doing the rendering, and so having it part of the kernel was critical, modern GPUs are so much more capable in terms of rendering than a typical CPU that you have this network interconnect in the form of PCIe and you more often than not have two very nearly distinct memory spaces, so it again is a triumph of multiprocessing over microkerneling (if that is even a word).