News for hackers. Stuff that matters.
Re:FreeBSD on Firecracker by yencabulator on Friday August 25, 2023 @03:16PM (#37265958)
Sort of. Let's say gVisor is three things:

1. Mechanism to capture syscalls (systrap)

2. Reimplementation of parts Linux kernel

3. Narrow set of calls to outside using Linux syscalls

This thing could be envisioned as

1. Linux syscall ABI as-is, same mechanism[a]

2. Reimplementation of parts Linux kernel

3. virt-io hardware drivers for calls to outside

So the middle part of the sandwich could look the same.

Also, I think it's worth saying that I think the work in maintaining #2 there is exactly why Google Cloud Run migrated away from gVisor. People just kept asking for more and more kernel features.

[a]: Alternatively, #1 could be replaced with unikernel like linking directly with #2.

Me personally, I think HTTP/3's move away from TCP could be really interesting for this sort of stuff. The responsibilities of the kernel could be hugely simplified if all you had were UDP/IP directly hardcoded to virtio (no need for routing, address configuration, ARP, etc), no paging etc, and the only filesystems were EROFS & tmpfs. Of course, Cloud Run's move away from gVisor shows that Enterprise clients would hate it.

There are no comments on this comment yet.