Re:IncludeOS: Run your C++ code directly on virtual hardware
by vezzy-fnord on Sunday October 18, 2015 @03:25PM
(#10409418)
Where the container virtualizes an instance of an operating system, the libOS (related: the unikernel and exokernel) goes further into virtualizing the operating system services and interfaces themselves. It's a logical step further.
[ Parent
| on HN ]
Re:IncludeOS: Run your C++ code directly on virtual hardware
by phire on Sunday October 18, 2015 @03:50PM
(#10409509)
One advantage is that the application gets full control over the page tables. At least one program I work on would gain huge advantages in that kind of environment.
Re:IncludeOS: Run your C++ code directly on virtual hardware
by vezzy-fnord on Sunday October 18, 2015 @04:18PM
(#10409621)
The same is true for microkernels, FWIW. As far back as Mach, a large advantage was separating the mechanism of VMM from the policy of handling page faults, which was done by external pagers in userspace.