Özgür Kesim
88f1455dd7
Instead of using cgo we call the syscall for BPF directly from go. The API hasn't changed, however, and we also closely follow the C-implementation as given in bpf(2). Not sure if this pure go variant is beneficial. Manual maintenance of all constants and structs upon changes of the BPF API would be necessary and cumbersome. We would at least need to complement this with auto-generation of constants and fields from /usr/include/linux/bpf.h. |
||
|---|---|---|
| .. | ||
| ebpf | ||
| symbolyze | ||
| .gitignore | ||
| main.go | ||