|
|
|
|
|
by yazaddaruvala
1285 days ago
|
|
lol, are you familiar with ring 0? what about context switching and scheduler preemption? If you are, then you know they add significant overhead to IO bound applications. > Why the hell would you put something like that in the kernel? Because some ridiculously large % of all client software is written in/transpiled to JavaScript? If the JS/WASM runtime would be run with the correct sandboxing (similar to browsers like Chrome), you likely could run the entire application in ring 0 and only context switch because of scheduling preemption. Maybe even ouch the whole browser into the kernel? All runtime APIs that currently need “syscalls” would become significantly more efficient. You’d end up with an extremely performant system for running browsers and browser like apps (ie Electron). |
|