From: patchwork-bot+netdevbpf@kernel.org
To: Ioana Lazea <ioana.lazea@canonical.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
stephen@networkplumber.org, dsahern@gmail.com,
jay.vosburgh@canonical.com
Subject: Re: [PATCH iproute2-next 0/2] tc/tbf and tc/htb: Allow 64 bit burst
Date: Sun, 05 Apr 2026 16:40:07 +0000 [thread overview]
Message-ID: <177540720754.1989033.9642319274974127990.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260323092918.11010-1-ioana.lazea@canonical.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Mon, 23 Mar 2026 09:29:11 +0000 you wrote:
> This patchset updates the TBF and HTB queuing discipline
> configurations to support burst sizes beyond the legacy 32-bit limits.
> As network interface speeds increase, the kernel’s internal
> representation of burst (calculated as time at a specific rate) can
> easily exceed the 4 GB threshold. These changes enable userspace to
> accommodate these larger values where the kernel API allows.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] tc/tbf: enable use of 64 bit burst
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=063071c4a8ba
- [iproute2-next,2/2] tc/htb: enable use of 64 bit burst
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=f6cb25efa1b2
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-04-05 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:29 [PATCH iproute2-next 0/2] tc/tbf and tc/htb: Allow 64 bit burst Ioana Lazea
2026-03-23 9:29 ` [PATCH iproute2-next 1/2] tc/tbf: enable use of " Ioana Lazea
2026-03-23 9:29 ` [PATCH iproute2-next 2/2] tc/htb: " Ioana Lazea
2026-04-05 16: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=177540720754.1989033.9642319274974127990.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=ioana.lazea@canonical.com \
--cc=jay.vosburgh@canonical.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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