-
Couldn't load subscription status.
- Fork 4
[PWCI] "[v1] net/mlx5: remove counter alignment" #257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The memory footprint was increased due to the alignment. Signed-off-by: Rongwei Liu <rongweil@nvidia.com> Signed-off-by: 0-day Robot <robot@bytheb.org>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideRemoved unnecessary cache-line alignment on hardware counter atomics in the mlx5 driver to simplify memory layout. Class diagram for updated mlx5_hws_cnt and mlx5_hws_cnt_state structuresclassDiagram
class mlx5_hws_cnt_state {
+RTE_ATOMIC(uint32_t) data
+uint32_t in_used:1
+uint32_t gen:7
+uint32_t query_gen:8
+uint32_t reserved:16
}
class mlx5_hws_cnt {
+struct flow_counter_stats reset
+mlx5_hws_cnt_state cnt_state
+RTE_ATOMIC(uint32_t) query_gen_when_free
}
mlx5_hws_cnt --> mlx5_hws_cnt_state
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
WalkthroughCache-line alignment specifications are removed from two atomic fields in MLX5 driver header structures. The Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey there - I've reviewed your changes - here's some feedback:
- Add a brief inline comment explaining why cache-line alignment was removed to help future maintainers understand the change.
- Run targeted benchmarks or profiling to ensure removing cache-line alignment does not introduce false‐sharing performance regressions.
- Verify that atomic alignment requirements are still met on all supported architectures after removing the explicit cache-line alignment.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Add a brief inline comment explaining why cache-line alignment was removed to help future maintainers understand the change.
- Run targeted benchmarks or profiling to ensure removing cache-line alignment does not introduce false‐sharing performance regressions.
- Verify that atomic alignment requirements are still met on all supported architectures after removing the explicit cache-line alignment.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
NOTE: This is an auto submission for "[v1] net/mlx5: remove counter alignment".
See "http://patchwork.dpdk.org/project/dpdk/list/?series=36485" for details.
Summary by Sourcery
Remove cache-line alignment from atomic counter fields in the mlx5 PMD to simplify structure layout
Enhancements:
Summary by CodeRabbit
Release Notes