4 ms·
Rapid development. There's probably things you'd get out of the latest Linux kernel's networking stack or video stack or btrfs driver or something, but your upg
by geofft 11y ago
Rapid development. There's probably things you'd get out of the latest Linux kernel's networking stack or video stack or btrfs driver or something, but your upgrade option is all-or-nothing, and you certainly don't to upgrade all of it. A microkernel could let you upgrade just the component you want to try a newer version of; it also means that there's a larger base of people like you testing the latest versions of each component, so the kernel improves more quickly.
Of course, this presupposes things about API compatibility/stability between microkernel components that may not be true in all microkernel designs.
- simoncion 11y agoI would expect that for some modules (networking, video, and FS can be loaded as modules) you can just put the new version of the module in a somewhat-earlier version of the kernel. I mean, if the ABI or internal kernel macros change, you're in for some porting work, but most of the kernel stuff can be configured as loadable modules. :)
- asuffield 11y agoIt sounds like a really cool idea, but to some extent we already have this with Linux out-of-tree modules - it doesn't work very well, but it's there, you can build a new version of the module, unload the old one, and load the new one. I suspect the microkernel version of this would be hard to implement for most of the same reasons, and probably fail in most of the same ways, which boil down to "APIs change a lot so things don't stay compatible for long".
- amelius 11y agoCan't we have some kind of compiler technology that allows us to have the advantages of both microkernels and unikernels?