"A look inside the BPF verifier [lwn]" https://news.ycombinator.com/item?id=41135371 https://news.ycombinator.com/item?id=41135371 eBPF: https://en.wikipedia.o

"A look inside the BPF verifier [lwn]" https://news.ycombinator.com/item?id=41135371 https://news.ycombinator.com/item?id=41135371 eBPF: https://en.wikipedia.org/wiki/EBPF https://en.wikipedia.org/wiki/EBPF "How are eBPF programs written?" https://ebpf.io/what-is-ebpf/#how-are-ebpf-programs-written https://ebpf.io/what-is-ebpf/#how-are-ebpf-programs-written : > In a lot of scenarios, eBPF is not used directly but indirectly via projects like Cilium, bcc, or bpftrace which provide an abstraction on top of eBPF and do not require writing programs directly but instead offer the ability to specify intent-based definitions which are then implemented with eBPF. > If no higher-level abstraction exists, programs need to be written directly. The Linux kernel expects eBPF programs to be loaded in the form of bytecode. While it is of course possible to write bytecode directly, the more common development practice is to leverage a compiler suite like LLVM [clang] to compile pseudo-C code into eBPF bytecode WASM eBPF for adblocking