⚡ Bolt: Batch producer wakeups in NAPI poll

[maxugly]

💡 What

Batches nata_wake_tx_peer calls outside the while loop and priv->lock spinlock in nata_poll.

🎯 Why

Calling nata_wake_tx_peer (which indirectly calls netif_wake_queue) inside a spinlock for every single dequeued packet is highly inefficient. It increases the time the spinlock is held and executes unnecessary redundant wakeups, leading to high contention in the hotpath.

📊 Impact

Reduces CPU cycles spent in spin_unlock/spin_lock and netif_wake_queue, significantly minimizing lock contention overhead and theoretically increasing networking throughput, especially during high-packet-rate scenarios (flood tests).

🔬 Measurement

Verified via static analysis and code review. Standard tests like nata-bench-once.sh would show higher TCP throughput due to reduced CPU overhead if a kernel test environment is available.

---

PR created automatically by Jules for task 5186029405788169018 started by @maxugly

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

Warning

Review limit reached

@maxugly, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 79a9fde4-a14f-4e37-b372-067d464714a2

📥 Commits

Reviewing files that changed from the base of the PR and between 6d5b3ed and fdee06c.

📒 Files selected for processing (2)

• .jules/bolt.md
• module/nata_net.c

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}