KAISER: hiding the kernel from user space
KAISER: hiding the kernel from user space
Posted Nov 16, 2017 18:34 UTC (Thu) by ttelford (subscriber, #44176)Parent article: KAISER: hiding the kernel from user space
Just the new instructions (CR3 manipulation) add a few hundred cycles to a syscall or interrupt
A few hundred cycles to a syscall or interrupt is vaguely similar to the basic IPC cost of the L4 microkernel. (200-300 cycles for amd64).
Kernels are not my area of expertise, so I have to ask: if a syscall is about to become as expensive as IPC on L4... would the (theoretical) performance of the respective kernels be similar after KAISER?
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
