(03) dpdk: batch ownership and safety - #1875
daniel-noland wants to merge 1 commit into
Conversation
MbufArray frees unused packets in bulk and transfers accepted TX packets to the PMD. This fixes double frees, dropped-RX leaks, and null Mbuf construction. Return unsent packets when TX stops making progress. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Daniel Noland <daniel@githedgehog.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe DPDK crate adds a fixed-capacity owning mbuf batch type. Bulk allocation, receive, and transmit APIs now use this type. Transmit returns packets that the PMD did not accept. ChangesDPDK mbuf batches
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to This change moves DPDK packet batches to an owning fixed-capacity type. It also returns packets the PMD did not accept instead of dropping them. No concrete merge-blocking risk was identified. Test coverage is acknowledged as deferred to a later PR in the stack. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 60.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 20 functions across 3 files. (1 skipped: 1 unsupported.)
Comment |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
I know that the coverage report for this is empty.
Fixing that in a practical way requires n-vm. That is fine, it just arrives later in the stack. I may be able to pull those tests back here. Still working on that. That said, the logic itself is ready for review.