From: patchwork-bot+netdevbpf@kernel.org
To: Carolina Jubran <cjubran@nvidia.com>
Cc: stephen@networkplumber.org, dsahern@gmail.com, jiri@nvidia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/2] Add support for traffic class bandwidth configuration via devlink-rate
Date: Fri, 11 Jul 2025 16:50:25 +0000 [thread overview]
Message-ID: <175225262514.2335070.1710754902601497445.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250704122753.845841-1-cjubran@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Fri, 4 Jul 2025 15:27:51 +0300 you wrote:
> This series adds support for configuring bandwidth allocation per
> traffic class (TC) through the devlink-rate interface. It introduces a
> new 'tc-bw' attribute, allowing users to define how bandwidth is
> distributed across up to 8 traffic classes in a single command. This
> enables fine-grained traffic shaping and supports use cases such as
> Enhanced Transmission Selection (ETS) as defined by IEEE 802.1Qaz.
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] devlink: Update uapi headers
(no matching commit)
- [iproute2-next,2/2] Add support for 'tc-bw' attribute in devlink-rate
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=c83d1477f8b2
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:[~2025-07-11 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 12:27 [PATCH iproute2-next 0/2] Add support for traffic class bandwidth configuration via devlink-rate Carolina Jubran
2025-07-04 12:27 ` [PATCH iproute2-next 1/2] devlink: Update uapi headers Carolina Jubran
2025-07-04 12:27 ` [PATCH iproute2-next 2/2] Add support for 'tc-bw' attribute in devlink-rate Carolina Jubran
2025-07-11 16:50 ` 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=175225262514.2335070.1710754902601497445.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cjubran@nvidia.com \
--cc=dsahern@gmail.com \
--cc=jiri@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.