3 ms·
The first example is of a network service which is what came to mind first for me. Traditionally the kernel logic handling sending/receiving the packets and the
by zamadatix 7y ago
The first example is of a network service which is what came to mind first for me. Traditionally the kernel logic handling sending/receiving the packets and the app run in different security contexts and there is a cost to hop back and forth. There has been a large amount of work over the years to optimize the data exchange for this use case but this eliminates the idea of a problem at all (while also being more minimal than any minimal normal OS could hope to be).
- zamalek 7y agoYou can also come up with more benefits by thinking alongs these lines, for example: the kernel doesn't need to keep track of which packets go to which process because there is only one process (the kernel itself). There could be a performance benefit thanks to this. > more minimal Which carries other benefits: boot time, memory overhead, etc. You could probably treat IncludeOS VMs like containers.