Re:Running Rust on the Rumprun Unikernel
by vezzy-fnord on Monday September 28, 2015 @09:12AM
(#10290248)
It would probably be the other way around, the programs making their own fine-grained policies from primitive kernel mechanisms. This has been an area of research for decades.
Multi-tenant assumptions probably aren't going away, since mainstream systems have by and large not been able to handle them.
Re:Running Rust on the Rumprun Unikernel
by hacknat on Monday September 28, 2015 @09:24AM
(#10290309)
In this case I meant that something of a runtime or additional code could be tacked on to programs when the compiler and/or run time sees that a program only computes in response to input, for example. In the case of unikernels, distinguishing parts of the "system" is an arbitrary line.
It'll be interesting to see what space unikernels take up in the coming years.
I think there is still a lot of fruitful territory to be explored in this space as traditional multi-user, multi-tenant assumptions can be thrown out the window. I think a big, unexplored advance that unikernels might be able to offer is the ability for the kernel-part to peek into the guts of what its programs are actually doing (at compile or run time) and make broader assumptions about scheduling.