Add four advanced runnable eBPF tutorial tools - #224
Conversation
|
Final dedicated review for exact head 41dff7e: NO BLOCKERS.\n\nReviewed the four tutorial implementations and bilingual rewrites, conflict resolution in the three repository-local skills, source-block synchronization, scope, version metadata, and KVM validation evidence. The reader-focused rewrite preserves complete kernel and user-space source while making the narrative follow each tool's real data flow. All four host builds and KVM scenarios passed; the final DNS refactor was rerun in KVM. No conflict markers, history deletion, relative-link regressions, or infrastructure/model/prompt leakage were found. |
|
Independent external review for exact head 41dff7e: NO BLOCKERS.\n\nThe review independently checked the three skill conflict resolutions, all four English/Chinese tutorials, byte-exact embedded source, program types and minimum-kernel claims, public sample-output provenance, CI scope, absolute links, and leakage constraints. It confirmed that the AF_XDP article now shows only output emitted by the public tool, all core kernel and user-space source remains complete, and the change set is proportional to four runnable advanced tutorials. The only nonblocking qualification is that the newest 6.16/7.1 APIs were exercised end to end on the shared Linux 7.2-rc4 KVM kernel rather than separately on every declared minimum kernel. |
|
Exact-head follow-up review is complete for The review found that the content-only workflow had removed technical-fidelity checks and that several rewritten passages no longer matched the implementations. The final head now:
Two independent final reviews found no actionable issues on the exact head. Documentation unit tests, source-block validator tests, generated indexes, internal links, punctuation/merge-marker scans, and AI-generated response; a maintainer will review and follow up later |
What changed
This PR adds four runnable eBPF tools with English and Chinese tutorials:
Each lesson includes a compact CLI, a deterministic integration test, the mechanism-relevant source and a link to the complete implementation, requirements, representative output from a real run, and primary upstream references.
The repository-local writing workflow keeps a single writer for reader-facing prose and avoids a mandatory second prose review for content-only work. It still requires implementation-aware fact checking of source excerpts, commands, behavior, versions, requirements, output, and relevant validation evidence.
Why
The examples fill four technical gaps in the tutorial series: DNS-derived connect policy, refcounted graph ownership with multiple indexes, reclaim profiling before an OOM kill, and a first standalone AF_XDP receive path. Each tool keeps the main kernel mechanism visible while still accepting a real cgroup or interface in normal mode.
Validation
git diff --checkpass.