4 ms·
> Or go the other way and have process-per-core with userland drivers and TCP state, where each process is just listening for interrupts and handles everything
by zbentley 9y ago
> Or go the other way and have process-per-core with userland drivers and TCP state, where each process is just listening for interrupts and handles everything from there?
A kernel. You are describing a kernel, minus workers, plus a web server.
- pjc50 9y agoI was thinking of things like https://shader.kaist.edu/mtcp/ https://shader.kaist.edu/mtcp/ , or https://github.com/snabbco/snabb https://github.com/snabbco/snabb or these kind of things: https://jvns.ca/blog/2016/06/30/why-do-we-use-the-linux-kernels-tcp-stack/ https://jvns.ca/blog/2016/06/30/why-do-we-use-the-linux-kern...