iovisor / iovisor/bcc

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

Open
#5,167 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
5d 13h
Merged PRs (30d)
3

Description

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.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with tools/cpudist.py and compare it with cpudist.bpf.c, cpudist.c, and cpudist.h to determine how the similarly named files relate. Document the purpose of each file and how the Python and C-based tools differ, so a beginner can understand why the files coexist.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, python
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.