3 ms·
I believe it is in fact correct that, at least as far as the market was concerned, one of the big reasons for the failure of microkernels in the mid-'90s was RP
by geofft 11y ago
I believe it is in fact correct that, at least as far as the market was concerned, one of the big reasons for the failure of microkernels in the mid-'90s was RPC overhead.
But it's no longer the mid-'90s, and everyone's been working on super efficient RPC (Cap'n Proto, msgpack, BSON, etc.) for unrelated problems. I have been suspecting for a while that a brand-new microkernel based firmly on mid-'10s technology (and targeting mid-'10s processors) would be perfectly performant.
- cvwright 11y agoYou're right that early microkernels (Mach) were pretty awfully slow. But that was really more the early 90's. Even before 2000 there were new systems that were already much, much faster than Mach. If you read the article, you'll see several references to papers that show microkernel performance on par with or better than traditional monolithic Unix systems. For example, "EROS: a fast capability system" by Shapiro, Smith, and Farber, in SOSP 1999. http://dl.acm.org/citation.cfm?doid=319151.319163 http://dl.acm.org/citation.cfm?doid=319151.319163
- mitchty 11y agoWhat intrigues me is the network stacks on linux for 40 gigabit network adapters ignore the kernel for as much as they can. Perhaps microkernels make more sense for our future hardware. Dunno just shooting from the hip here.
- toast0 11y agoI don't have a lot of experience with microkernels, but I would imagine the objections due to communication are not a result of serialization of the communications; they would tend to be C structs, more or less, not a terrible XML document, creating them wouldn't be a significant performance issue, although actually doing the IPC may be a performance problem (or may be perceived to be). I think the market issue for microkernels is that a) there aren't a lot of choices for microkernels that are 'production ready', today I could reasonably run a website on Windows NT, or OS X, but the Hurd is perpetually not ready. b) Monolithic kernels are 'good enough'. The benefits microkernels promise don't really make a huge impact (or aren't perceived to). Yes, it would be great if my filesystem driver didn't crash the whole system when it crashes, but if it crashes in a microkernel, I expect I would still have to restart all the processes that had open files, because the state is lost; and either way, I'd rather not have my filesystem driver crash. Most users of monolithic kernels don't spend a lot of time developing or debugging kernel drivers, so developer efficiency there doesn't really pay off. Most of the problems I track down to a kernel issue are things that could be equally present in either style kernel: bugs/inefficiencies in the tcp stack, stupid disk controller resource leaks, etc. Maybe it would be easier to track them down if the tcp process was clearly spinning on all the cpu, or the disk controller process had a ton of ram/resources assigned to it, but it's not that hard to track things down anyway -- figuring out why they're broken is much harder than figuring out where they're broken.
- asynchronous13 11y agoa) there are microkernel-based operating systems that are available right now. QNX and Green Hills, for example. There aren't any free ones that I know about, so the cost might be hindering adoption. b) agree with you on this point that monolithic is 'good enough' these days. There are specific benefits to my particular application, but for a general desktop user I don't see the point. Even on a server the benefits are not very visible.
- collyw 11y ago"but the Hurd is perpetually not ready" People used to say the same about Perl 6! :)