Learn Fast
Reviewing is the fastest way to understand how production-grade systems code actually works. Real decisions, not textbook examples.
Low Pressure
A review can be one sentence. A question, an observation, or a test result, any of these is a genuine contribution.
Real Impact
Your feedback becomes part of the permanent project record. Good reviews catch bugs and make the codebase better for everyone.
Three Steps, No Setup Required.
No account needed to browse. No commit access needed to contribute.
Step 1: Open Patchwork
Patchwork is where all submitted DPDK patches live. Browse recent submissions and look for something small and self-contained that matches your interests.
Step 2: Read a Patch
Start with the description — it explains what changed and why. Then look at the code. Does it do what it says? Is anything confusing? Are there edge cases the author might have missed?
Step 3: Send a Reply
Click through to the email thread and share what you noticed. A question, an observation, or a test result — any of these counts. If you have the repo, run devtools/checkpatches.sh on the patch before you reply.
What a Good Review Looks Like
The kinds of comments that actually make a difference. None of them are long:
Testing
“I tested this on [hardware] and it worked, no regressions on my setup.”
Clarity
“The conditional in lines 45–52 is hard to follow. Could this be a helper function?”
Edge Case
“What happens when the buffer pointer is null here? Looks like an unhandled path.”
Not Sure What to Look For?
The DPDK Review Assistant explains patches in plain language and helps you understand what matters — ABI changes, performance implications, missing tests. It won’t write your review, and it will tell you exactly why you shouldn’t post what it generates. It’s a reading aid, not a shortcut.
Ready to Contribute?
The hardest part is opening the first patch. Everything after that is just reading, thinking, and maybe asking a question.
