Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Confused about libbpf-tools:since we have the .py tools, why do we still need libbpf-tools? #5167

Open
violence-max opened this issue Dec 12, 2024 · 3 comments

Comments

@violence-max
Copy link

Using tools/cpudist.py as an example, there are other files with similar names, such as cpudist.bpf.c, cpudist.c, and cpudist.h. Moreover, nearly all tools have corresponding files with .c, .bpf.c, and .h extensions. At one point, I thought cpudist.bpf.c was directly embedded and executed within cpudist.py. This is quite unfriendly for beginners, as I couldn’t figure out the purpose or significance of the cpudist C source code files.

@ekyooo
Copy link
Contributor

ekyooo commented Dec 26, 2024

I hope the Useful links on the page below will be helpful to you.
https://github.com/iovisor/bcc/tree/master/libbpf-tools#readme

@chenhengqi
Copy link
Collaborator

Also check Andrii's blog https://nakryiko.com/posts/bpf-portability-and-co-re/

@chenhengqi
Copy link
Collaborator

As for beginner-friendly, I would recommend bpftrace.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants