From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <hangbin.liu@linux.dev>
Cc: jv@jvosburgh.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, razor@blackwall.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, liuhangbin@kylinos.cn
Subject: Re: [PATCH net v6 0/2] bonding: fix TLB load-tracking overflow on high-speed NICs
Date: Thu, 03 Sep 2026 01:40:46 +0000 [thread overview]
Message-ID: <178839964638.3035212.18319346859188777128.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831-bond_overflow-v6-0-ffb0ed1f7268@kylinos.cn>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 31 Aug 2026 09:50:58 +0800 you wrote:
> The bonding TLB (Transmit Load Balancing) mode tracks per-slave and
> per-client transmit byte counts in u32 fields. At sustained throughput
> above ~3.2 Gbit/s over the 10-second rebalance interval these counters
> wrap, causing compute_gap() to produce incorrect gap values and
> mis-select transmit slaves. Such speeds are routine on modern NICs
> under heavy traffic.
>
> [...]
Here is the summary with links:
- [net,v6,1/2] bonding: convert unbalanced_load to per-cpu state
https://git.kernel.org/netdev/net-next/c/e14761563588
- [net,v6,2/2] bonding: fix u32 overflow in compute_gap()
https://git.kernel.org/netdev/net-next/c/4cef95f72bbd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-03 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 1:50 [PATCH net v6 0/2] bonding: fix TLB load-tracking overflow on high-speed NICs Hangbin Liu
2026-08-31 1:50 ` [PATCH net v6 1/2] bonding: convert unbalanced_load to per-cpu state Hangbin Liu
2026-08-31 1:51 ` [PATCH net v6 2/2] bonding: fix u32 overflow in compute_gap() Hangbin Liu
2026-09-02 1:48 ` [PATCH net v6 0/2] bonding: fix TLB load-tracking overflow on high-speed NICs Jay Vosburgh
2026-09-03 1:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178839964638.3035212.18319346859188777128.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hangbin.liu@linux.dev \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox