3 ms·
I believe your two examples are actually two entirely different paradigms. The first one is based on the exokernel notion. A bit muddy, but it seems that nobody
by contingencies 13y ago
I believe your two examples are actually two entirely different paradigms. The first one is based on the exokernel notion. A bit muddy, but it seems that nobody has ever used a pure exokernel successfully at scale in industry, presumably because it seems to call for the kernel exposing hardware directly to userland code whilst simultaneously managing multiple tenants. Basically, the idea seems like a sort of early and poorly articulated call to modern OS level resource management (eg. cgroups).
Your example two, the zerg system, seems very similar to LXC. Other than the exoticism of Erlang, their only big feature vs. normal paravirtualization seems to be startup time, which they see as a groundbreaking change. Well, I regularly start whole systems in LXC in fractions of a second. See https://github.com/globalcitizen/lxc-gentoo https://github.com/globalcitizen/lxc-gentoo
In summary, these two projects are not really any different to the topic under discussion, ie. LXC (~cgroups/namespaces). Well, except that unlike cgroups/namespaces they're not necessarily able to run everywhere Linux runs!
- vidarh 13y agoThe Mirage link is confusing matters. Mirage appears to be an exo/micro kernel for running in a para-virtualized system. That's very different from an exo-kernel running on bare hardware. With Mirage, what the apps run on seems to be "para-virtualized bare metal", so rather than using the POSIX syscall interface as its ABI, it's using the paravirtualized "hardware" as its ABI. That makes Mirage very similar to Zerg - it's the same concept, only OCaml vs. Erlang. As for LXC, I agree LXC offers a lot of this, especially since you don't need to boot full Linux environments - you can spawn individual applications and fine-tune what isolation you need. Or you can even build applications that explicitly use cgroups themselves to isolate sub-processes. So their "spawn one Xen Dom-U per request" demo could similarly have been a "spawn one new process isolated in its own cgroups". But these systems are appealing to me in that they bring VM level isolation with startup performance and resource utilization more in line with container systems. That's particularly appealing if we start seeing cloud systems that can handle it. Imagine being able to create new EC2 instances at sub-second times...