4 ms·
I don't understand what the value is in writing a new original microkernel from scratch in this day and age when sel4* is free and open source, performance tune
by cmrdporcupine 10y ago
I don't understand what the value is in writing a new original microkernel from scratch in this day and age when sel4* is free and open source, performance tuned for 20ish years, is security hardened, and is provably correct for both security and features?
This doesn't seem like a wise path to take.
* See http://sel4.systems/ http://sel4.systems/
- aanm1988 10y agoYou are asking why NIH is a problem for a project that seems to be at least partly driven by NIH?
- bitmapbrother 10y agoThe micro-kernel used by Fuchsia is not built from scratch. It's based on a heavily modified version of the LK kernel.
- naasking 10y agoNo kidding. All kinds of robust operating system design went into seL4. It's simply crazy not to make use of it. I can see potential problems already from looking at the Magenta kernel docs. For instance, they say that all syscalls are non-blocking except for explicit wait and sleep calls, which means the kernel is very likely vulnerable to various DoS attacks, which aren't a problem for L4 kernels.
- kjksf 10y agoI know nothing about differences between fuchsia and sel4 but it would be rather strange if something as complicated as a OS kernel wouldn't have many parts where you have to make trade-offs. People compete fiercely in the field of todo applications, I don't see why there shouldn't be competition in microkernel space. Things changed in hardware in last 20 years and maybe we've learned something about software as well. Not to mention that sel4 is GPLv2, which is kind of problematic for a commercial company. In the end, the micro-kernel is a very small part of the whole stack.
- nickpsecurity 10y agoI think author meant L4 kernels were performance tuned for 20 years to be the fastest. Then, one using applying such lessons was mathematically verified for correctness down to assembly. It's proprietary and open-source depending on what your end product will be. They'd probably even add features to it for a Google-specific version that leveraged as many proven compinents as possible.
- pjmlp 10y agoAnd most of us have a mobile phone running OKL4 on the radio CPU.
- qznc 10y agoSeL4 is still working on multithreading. It is probably not good enough for a user interfacing OS yet.
- nickpsecurity 10y agoThat's true in its current state. Remember, though, that they're working on multithreading in a way that ties into their proof from high-level spec down to the code down to the assembly. Googles people are just putting together a kernel with review & testing. They could take seL4, modify it for concurrency, check it with concurrency-related tooling, and still get quite a bit of assurance from original work. Proof no longer applies but most things it applied to haven't changed. And model-checkers for concurrency are among easiest tools to use in formal verification w/ TLA+ getting adoption even by mainstream companies.
- deleted 10y ago[deleted]