3 ms·
Because it passes more boundaries and stuff. But hey, I didn’t code a Webserver so far - so what do I know. :D AFAIK eBPF can be hardware offloaded. If you ha
by augunrik 4mo ago
Because it passes more boundaries and stuff.
But hey, I didn’t code a Webserver so far - so what do I know. :D
AFAIK eBPF can be hardware offloaded. If you have the use case.
- someothherguyy 4mo ago> But hey, I didn’t code a Webserver so far - so what do I know If you limit the scope, its worth doing and might not take as much effort as you might think. You could possibly find some enjoyment and learn a few things doing so.
- solid_fuel 4mo agoIn college I had a networks class where the capstone project was writing a basic HTTP server in C. It's actually shockingly easy, especially if you're only supporting get, and fetch. Mine was something like 70 lines, and would just listen on 8080 and fork when it got a connection before checking for the requested file and sending it or a 404. I was immediately tempted to try adding something like CGI support but didn't have the time that semester.
- tracker1 4mo agoSeconded, HTTP and event HTTPS to some extent isn't so bad to wireup... HTTP2/3/QUIC is another story IMO though.
- rciorba 4mo agoThis is not in-kernel eBPF, this is a userspace eNPF runtime, so I don't see why it would pass fewer boundaries