Rump kernel: Difference between revisions
m (actually correct minios link!) |
(→Resources: name link) |
||
| Line 7: | Line 7: | ||
==Resources== |
==Resources== |
||
Documentation and source code is linked from [http://www.rumpkernel.org/]. The main build tool for building Xen applications is [https://github.com/rumpkernel/rumprun]. |
Documentation and source code is linked from [http://www.rumpkernel.org/]. The main build tool for building Xen applications is rumprun[https://github.com/rumpkernel/rumprun]. |
||
There is an introduction in USENIX ;login: magazine October 2014.[http://rumpkernel.org/misc/usenix-login-2014/login_1410_03_kantee.pdf]. |
There is an introduction in USENIX ;login: magazine October 2014.[http://rumpkernel.org/misc/usenix-login-2014/login_1410_03_kantee.pdf]. |
||
Revision as of 15:20, 24 June 2015
The rump kernel is a NetBSD project that allows kernel drivers to be repurposed, specifically it allows applications to be linked into standalone unikernels that run on the Xen hypervisor.
Essentially application code, the C library, kernel drivers for the network stack, and Xen PV (or HVM) drivers and some Mini-OS boot code are linked into a single executable that can be run directly under Xen without an operating system. The resulting unikernel is small (often a few megabytes), fast to boot, and only contains the minimal dependencies necessary to run.
This is similar to MirageOS, but supports many existing Posix applications, rather than OCaml applications targeting Mirage.
Resources
Documentation and source code is linked from [1]. The main build tool for building Xen applications is rumprun[2].
There is an introduction in USENIX ;login: magazine October 2014.[3].
