Deprecate the library part and integrate the BCC Go-bindings in the BCC repo #304
Comments
margamanterola
changed the title
ti-mo
added a commit
to ti-mo/cilium
that referenced
this issue
Jan 31, 2022
As it's been unmaintained for a while, and there are talks [0] of officially deprecating gobpf, I guess it's time to remove it here. I was hinted by a fellow community member that this list might need a bit of work (or we could just redirect to ebpf.io instead), but cilium/ebpf should at least be mentioned here for now. [0]: iovisor/gobpf#304 Signed-off-by: Timo Beckers <[email protected]>
glibsm
pushed a commit
to cilium/cilium
that referenced
this issue
Jan 31, 2022
As it's been unmaintained for a while, and there are talks [0] of officially deprecating gobpf, I guess it's time to remove it here. I was hinted by a fellow community member that this list might need a bit of work (or we could just redirect to ebpf.io instead), but cilium/ebpf should at least be mentioned here for now. [0]: iovisor/gobpf#304 Signed-off-by: Timo Beckers <[email protected]>
|
Is there any plan on moving the go binding parts to bcc repo? |
|
Would like to see this happen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This repo has two parts: go bindings for the bcc framework, and low-level routines to load and use eBPF programs from .elf files.
It has been unmaintained for a while, which means that for the low-level routines, cilium/ebpf does a better job and should be used instead of this one. For the bcc go-bindings, they are still useful, but it doesn't make sense to have them in this repo. They should be in the bcc repo together with the bindings for other languages.
So, the plan is to deprecate the low-level routines and move the other code to the other repo. If someone has any reason to object to either of those, please let us know.
The text was updated successfully, but these errors were encountered: