3 ms·
Always good to see that some systems still do some engineering. Linux has lost this. It got so complex that only small patches get in, so the hacks continue to
by snvzz 7y ago
Always good to see that some systems still do some engineering. Linux has lost this. It got so complex that only small patches get in, so the hacks continue to stack up.
OpenBSD does interesting stuff like this or pledge(2) and unveil(2).
Dragonfly does interesting stuff like their concurrent lockfree/lockless servers approach instead of using kernel locks, and HAMMER2[0].
Genode[1][2] implements multiserver systems supporting many kernels including seL4, making good use of capabilities.
[0]: https://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys/vfs/hammer2/DESIGN https://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/sys...
[1]: https://www.genode.org https://www.genode.org
[2]: https://www.genodians.org https://www.genodians.org
- burfog 7y agoLinux has plenty of engineering. Of course that doesn't mean identical features. Linux has a VFS with lockless path lookups. The push to get Linux running on machines like the SGI Altix, with at least 10240 cores running one shared instance of the kernel, has really helped with locking issues. Another factor has been the push for real-time performance, with and without choosing the option to make the kernel preemptable.
- snvzz 7y agoAnd all of this is based on hacks and ugly workarounds, due to the kernel being a monolithic design. When the kernel isn't monolithic, kernel preemption isn't necessary, or worth it[0]. Imagine if instead of the, I argue insane, complexity added by the fine-grained SMP locks and the unholy mess that is kernel preemption, the kernel had been split into separate processes, which maps to SMP cleanly. Actually, I don't have to imagine it, because that's what Dragonfly has been progressively doing since they forked FreeBSD, and what microkernel multiserver systems like Genode/seL4 or HelenOS are from the get-go. It turns out, despite having very little manpower (which is why they chose to focus on x86-64), Dragonfly has performance and scalability competitive to Linux today. Imagine if they had more people. I will not be too surprised when Dragonfly finally leaves Linux in the dust and people wonder how the hell, which is something I predict will happen. Linux hit a ceiling despite all the money thrown into it. Dragonfly hasn't yet. [0]: http://ts.csiro.au/publications/nicta_full_text/5859.pdf http://ts.csiro.au/publications/nicta_full_text/5859.pdf
- dntbnmpls 7y ago> And all of this is based on hacks and ugly workarounds, due to the kernel being a monolithic design. But most BSD ( including OpenBSD which you just praised ) is monolith as well. > I will not be too surprised when Dragonfly finally leaves Linux in the dust and people wonder how the hell, which is something I predict will happen. Dragonfly would have to first leave FreeBSD in the dust before taking on all the linux distros. Microkernels are great for learning about kernels. Monoliths have been great for general and corporate use. Perhaps the future is hybrid, only time will tell.
- snvzz 7y ago>Dragonfly would have to first leave FreeBSD in the dust before taking on all the linux distros. You're late to the party, as Dragonfly is already outdoing Linux in some areas, such as the network stack[0]. >But most BSD ( including OpenBSD which you just praised ) is monolith as well. I praised them for the engineering they've been doing. They still retain flexibility, despite the monolithic design. Linux went all-in with their smp locking and kernel preemption, and the costs of getting any work done on the source code have skyrocketed since. >Perhaps the future is hybrid, only time will tell. Hybrid is a marketing term. It's a blurry line between a monolith and a so-called hybrid. What they're marketing is structure. Structure is good. Netbsd is an example of a well structured system. Linux is the counterpart: A poorly structured one. >Monoliths have been great for general and corporate use. UNIX is an old design. Corporate hates taking risks. However, there's massive scale deployments of microkernel systems, they're just not on your face; the visibility is actually quite low for these. But they do tasks that greatly benefit from or outright require such a design. Monolithic design limits are more evident than ever, as we're hitting them left and right. So this is changing. For instance, besides systems such as Genode and HelenOS, Google is working on Fuchsia and Huawei on HarmonyOS. Brace for impact, as waves will be made when this all finally hits. [0]: https://leaf.dragonflybsd.org/~sephe/perf_cmp.pdf https://leaf.dragonflybsd.org/~sephe/perf_cmp.pdf
- jayp1418 7y agoMaybe rump kernels might be future : https://research.csiro.au/tsblog/using-rump-kernels-to-run-unmodified-netbsd-drivers-on-sel4/ https://research.csiro.au/tsblog/using-rump-kernels-to-run-u...