From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
petrm@nvidia.com, jiri@nvidia.com, mlxsw@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next 0/3] mlxsw: Offload root TBF as port shaper
Date: Fri, 29 Oct 2021 03:10:09 +0000 [thread overview]
Message-ID: <163547700901.18853.9697116912833662953.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027152001.1320496-1-idosch@idosch.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Oct 2021 18:19:58 +0300 you wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> Petr says:
>
> Egress configuration in an mlxsw deployment would generally have an ETS
> qdisc at root, with a number of bands and a priority dispatch between them.
> Some of those bands could then have a RED and/or TBF qdiscs attached.
>
> [...]
Here is the summary with links:
- [net-next,1/3] mlxsw: spectrum_qdisc: Offload root TBF as port shaper
https://git.kernel.org/netdev/net-next/c/48e4d00b1b93
- [net-next,2/3] selftests: mlxsw: Test offloadability of root TBF
https://git.kernel.org/netdev/net-next/c/3d5290ea1dae
- [net-next,3/3] selftests: mlxsw: Test port shaper
https://git.kernel.org/netdev/net-next/c/2b11e24ebaef
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:[~2021-10-29 3:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 15:19 [PATCH net-next 0/3] mlxsw: Offload root TBF as port shaper Ido Schimmel
2021-10-27 15:19 ` [PATCH net-next 1/3] mlxsw: spectrum_qdisc: " Ido Schimmel
2021-10-29 3:08 ` Jakub Kicinski
2021-10-29 9:58 ` Petr Machata
2021-10-27 15:20 ` [PATCH net-next 2/3] selftests: mlxsw: Test offloadability of root TBF Ido Schimmel
2021-10-27 15:20 ` [PATCH net-next 3/3] selftests: mlxsw: Test port shaper Ido Schimmel
2021-10-29 3:10 ` 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=163547700901.18853.9697116912833662953.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).