News for hackers. Stuff that matters.
Re:Autonomous Rust Unikernels in Google Cloud by orf on Saturday January 11, 2020 @08:06PM (#22023662)
> Even trivial hello world style of apps can use north of 30-40 different types of syscalls

I'd wager a lot of those are irrelevant in a unikernel world. Some of those might be dealing with ttys, or setting terminal attributes, or other needless things.

Re:Autonomous Rust Unikernels in Google Cloud by eyberg on Saturday January 11, 2020 @08:24PM (#22023764)
you're absolutely correct - in cases like that they become nops, however, if you don't have at least stubs you can't load unmodified software which imo is a imperative for any type of mass adoption

Drew DeVault had a recent blogpost on this very subject -> https://drewdevault.com/2020/01/04/Slow.html

however, when we were adding support for various language runtimes I was surprised at how much (ab)use there was where certain calls were used in a very very different manner than what was intended - for instance one might wonder why we have limited pipe support if we don't have the notion of multiple processes - cause ruby uses it to communicate from the main vm thread to the user thread - it's little gems like this that you simply won't know until you try to support it

then there's the cases where you might support one type of syscall but there's another syscall exactly like it except it has one additional argument

Re:Autonomous Rust Unikernels in Google Cloud by sitkack on Sunday January 12, 2020 @01:07AM (#22024766)
I could see a lazy libc that elides syscalls until later in the evolution of a program so that the perf hit isn't paid until it is actually needed. Especially if you can detect when the program is finished, so the cleanup code can be skipped, destroying the entire execution environment. `fast_exit(42)`