3 ms·
Right here. https://nanovms.com https://nanovms.com If you like kernel level c I'm hiring. The best hackers want to work with the best hackers and we are char
by eyberg 4y ago
Right here.
https://nanovms.com https://nanovms.com
If you like kernel level c I'm hiring. The best hackers want to work with the best hackers and we are charting a new course for the 2020s - not one from the 1960s. Despite what you might read in the main-stream dev news our work is extremely important and needs people just like you.
You don't have to work at a boring corporate job -- you can instead work at the unikernel company NanoVMs - you just need to email me.
- _xrp0 4y agoHey, can you speak a bit about how nanos compares to something Like unikraft? IIRC nanos doesn't eliminate syscalls in it's entirety like other unikernels.
- eyberg 4y agoWe don't think that's a defining characteristic no. We keep the kernel/user cause otherwise you can very very easily change page permissions which means all security goes out the window. You could instantly make rwx on all pages with a few instructions. If you rewind to ~ 2013 most unikernels were talking about trashing the context switch yet depending on the "context" that implies various things (kthread <> kthread, user proc <> user proc, user thread <> user thread, etc...) They all have different costs and while we definitely agree with the aggressive cost of various user process to user process the kernel <> user was one we felt was not worth trashing. Clearly though, because of massive adoption, we see 200% extra throughput on GCP and up to 300% on AWS - so the performance and security remain.