EBPF: Difference between revisions
No edit summary |
|||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
eBPF (Enhanced [https://en.wikipedia.org/wiki/Berkeley_Packet_Filter Berkeley Packet Filter]) is a powerful | eBPF (Enhanced [https://en.wikipedia.org/wiki/Berkeley_Packet_Filter Berkeley Packet Filter]) is a powerful Linux kernel mechanism allowing bytecode to be attached to dynamic points in kernel and userspace, and implementing JIT of said bytecode to the host ISA, all on the fly using a running kernel. It builds atop [[kprobes]], and is in the same family of tools as SystemTap and DTrace. It is driven through the [http://man7.org/linux/man-pages/man2/bpf.2.html <tt>bpf(2)</tt>] system call, though it is usually more convenient to employ the libbpf library and <tt>bpftool</tt> binary. eBPF supports its own BTF debugging information, a simplified form of [[DWARF]]. | ||
eBPF | The BCC (BPF Compiler Collection) toolchain is capable of compiling high-level languages (a restricted C, Lua, etc.) into eBPF bytecode, and provides a high-level Python infrastructure around eBPF. <tt>bpftrace</tt> provides an awk-like language geared towards eBPF "one-liners." The [[XDP|eXpress Data Path (XDP)]] is built atop eBPF. | ||
==Tools== | ==Tools== | ||
* <tt>bpftrace</tt> provides a terse DSL that looks an awful lot like awk, allowing simple eBPF programs to be instantiated and attached directly from the command line. | * <tt>bpftrace</tt> provides a terse DSL that looks an awful lot like awk, allowing simple eBPF programs to be instantiated and attached directly from the command line. | ||
* <tt>llvm-readelf</tt> can analyze an ELF object, including those targeting eBPF | |||
* <tt>llvm-objdump</tt> can disassemble an ELF object to eBPF bytecode | * <tt>llvm-objdump</tt> can disassemble an ELF object to eBPF bytecode | ||
===bpftool=== | |||
<tt>bpftool</tt> can be built in <tt>tools/bpf</tt> of the installed kernel's source. | |||
{|class="wikitable" | |||
! Subcommand !! Role | |||
|- | |||
| feature || examines the running kernel, and enumerates all capabilities present related to eBPF (program types, map types, kernel config options, eBPF helpers, etc.) | |||
|- | |||
| prog || enumerates attached eBPF programs, loads and attaches programs, and can dump loaded programs' bytecode (or JITted host code) | |||
|- | |||
| perf || lists [[kprobes]] and other tracepoints with attached programs | |||
|- | |||
| map || enumerates and manipulates maps | |||
|- | |||
|} | |||
===[[perf]]=== | |||
Kernel 4.4 added general events to the [[perf]] infrastructure. Kernel 4.9 added the ability for eBPF to register perf events. These are the preferred method for streaming events to userspace from an eBPF program. | |||
==Compiling eBPF== | ==Compiling eBPF== | ||
| Line 25: | Line 42: | ||
* zoidbergwill's [https://github.com/zoidbergwill/awesome-ebpf awesome-ebpf] list | * zoidbergwill's [https://github.com/zoidbergwill/awesome-ebpf awesome-ebpf] list | ||
* BCC [https://github.com/iovisor/bcc/blob/master/docs/reference_guide.md reference guide] | * BCC [https://github.com/iovisor/bcc/blob/master/docs/reference_guide.md reference guide] | ||
* [https://github.com/iovisor/bcc/blob/master/docs/kernel-versions.md Kernel versions] supporting various features | |||