| ▲ | bewo001 an hour ago | |
with ebpf, I'd argue it's getting closer to an exokernel (https://sites.cs.ucsb.edu/~rich/class/cs270/papers/dawson-ex...) micro kernel: a bit like microservices; eth process talks to ip process, ip process talks to tcp process, tcp process talks to web server; multiple IPCs per packet/PDU, rather slow, single crashing process can still take out everything. exo kernel: web server asks kernel to get packets matching some filter, kernel passes packets matching the filter to web server, web server uses a eth/ip/tcp library to process the packets; | ||
| ▲ | cowlevel 30 minutes ago | parent [-] | |
My favourite one-sentence explanation of an exokernel was from the explanation of a web server called Cheetah running on a kernel called XOK: to save time, the web server stores preformatted TCP packets on disk. This one sentence is such a profound layering violation that it changes your perspective on the possible ways to write programs. | ||