News for hackers. Stuff that matters.

A comment on The Case for a High-Level Kernel-Bypass I/O Abstraction. Parent comment

Re:The Case for a High-Level Kernel-Bypass I/O Abstraction by pjmlp on Thursday May 23, 2019 @05:42AM (#19990096)
Well, that is the whole point of unikernels.

Memory safe languages with rich runtimes, only need a mini kernel to run bare metal.

Windows has been pushing for user space drivers for a while now, including GPUs.

Android is following the same path with Project Treble, and who knows what will happen with Fuchsia.

Likewise on many high integrity OSes for embedded deployment.

[ Parent | on HN ]
Re:The Case for a High-Level Kernel-Bypass I/O Abstraction by gigatexal on Thursday May 23, 2019 @09:27AM (#19991536)
Does such a runtime and ecosystem exist for go, and if not, (even if so) what other languages?
[ Parent | on HN ]
Re:The Case for a High-Level Kernel-Bypass I/O Abstraction by pjmlp on Thursday May 23, 2019 @10:11AM (#19991954)
Java has baremetal deployments on the embedded space, PTC and Aicas are the two most well known ones.

.NET has netduino and eventually meadow, although it is a subset.

Erlang has GRiSP.

OCaml has MirageOS.

To come back to your question, Go has tinyGo, gVisor, emgo, Biscuit.

And you can have a look at this as well, https://nanovms.com/dev/tutorials/running-go-unikernels

And here http://unikernel.org/projects/

[ Parent | on HN ]