Re:Snap: A Microkernel Approach to Host Networking
by geofft on Monday October 28, 2019 @07:34AM
(#21375991)
It works by defining "process" in a way that doesn't imply "registers and cache." If the concern is the ability for one process to survive despite arbitrary misbehavior from another process (and not, say, Spectre-style attacks), software-based fault isolation like NaCl or PittSFIeld or using a restricted language runtime like wasm or Lua demonstrably works fine for that, no hardware context switch required.
[ Parent
| on HN ]
Re:Snap: A Microkernel Approach to Host Networking
by hvidgaard on Monday October 28, 2019 @08:11AM
(#21376152)
That sounds like a lot of overhead for a kernel. There is a reason it's normally written in a mix of C and ASM.
Re:Snap: A Microkernel Approach to Host Networking
by zaarn on Monday October 28, 2019 @08:26AM
(#21376225)
It wouldn't be that much overhead in reality, you can still write the kernel in a mix of C and ASM (or more modern; Rust and ASM). The kernel doesn't even need to know about these isolation mechanisms, since you run stuff in ring 0, you can hook the appropriate APIs and interfaces in a process. The kernel itself would be insanely small and thusly more easy to defend.