3 ms·
If eBPF is new to you (it was to me), this article offers some useful context to help parse "eBPF brings to the Linux kernel what JavaScript brought to the bro
by corford 6y ago
If eBPF is new to you (it was to me), this article offers some useful context to help parse "eBPF brings to the Linux kernel what JavaScript brought to the browser" (which made me shudder at first): https://thenewstack.io/how-io_uring-and-ebpf-will-revolutionize-programming-in-linux/ https://thenewstack.io/how-io_uring-and-ebpf-will-revolution...
- cdsccd 6y agoThere was also a more recent one on eBPF and Kubernetes which was an interesting read: https://thenewstack.io/ebpf-put-the-kubernetes-data-plane-in-the-kernel/ https://thenewstack.io/ebpf-put-the-kubernetes-data-plane-in...
- tgraf 6y agoAnother good way to get started is https://ebpf.io/ https://ebpf.io/. It features pointers that go beyond just networking and also cover usage of use cases involving tracing, profiling, security, ...
- sytse 6y agoWhat do people think about this way to explain eBPF: Microkernels were presented as the future in which fewer things would run in the kernel. Instead we've gone in the other direction in which more is running inside the kernel. Monolithic kernel: the Network Device runs inside the kernel and the Packet Filter outside. Microkernel: both the Network Device and Packet Filter run outside the kernel. eBPF: both the Network Device and the Packet Filter run inside the kernel.
- deleted 6y ago[deleted]
- corford 6y agoYep, that seems pretty spot on. Not sure yet how I feel about allowing sandboxed user code in the kernel (my gut doesn't like the idea) but much smarter people than me seem to think it makes sense so I guess time will tell.