From: Leon Romanovsky <leon@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>, Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next V5 00/11] net/mlx5: ConnectX-8 SW Steering + Rate management on traffic classes
Date: Thu, 5 Dec 2024 11:23:55 +0200 [thread overview]
Message-ID: <20241205092355.GX1245331@unreal> (raw)
In-Reply-To: <20241204220931.254964-1-tariqt@nvidia.com>
On Thu, Dec 05, 2024 at 12:09:20AM +0200, Tariq Toukan wrote:
> Hi,
>
> This patchset starts with 4 patches that modify the IFC, targeted to
> mlx5-next in order to be taken to rdma-next branch side sooner than in
> the next merge window.
>
> This patchset consists of two features:
> 1. In patches 5-6, Itamar adds SW Steering support for ConnectX-8.
> 2. Followed by patches by Carolina that add rate management support on
> traffic classes in devlink and mlx5, more details below [1].
>
> Series generated against:
> commit bb18265c3aba ("r8169: remove support for chip version 11")
>
> Regards,
> Tariq
<...>
> Carolina Jubran (6):
> net/mlx5: Add support for new scheduling elements
>
> Cosmin Ratiu (2):
> net/mlx5: ifc: Reorganize mlx5_ifc_flow_table_context_bits
> net/mlx5: qos: Add ifc support for cross-esw scheduling
>
> Yevgeny Kliteynik (1):
> net/mlx5: Add ConnectX-8 device to ifc
I applied these IFC patches to our mlx5-next shared branch.
https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/log/?h=mlx5-next
Thanks
next prev parent reply other threads:[~2024-12-05 9:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 22:09 [PATCH net-next V5 00/11] net/mlx5: ConnectX-8 SW Steering + Rate management on traffic classes Tariq Toukan
2024-12-04 22:09 ` [PATCH mlx5-next V5 01/11] net/mlx5: ifc: Reorganize mlx5_ifc_flow_table_context_bits Tariq Toukan
2024-12-04 22:09 ` [PATCH mlx5-next V5 02/11] net/mlx5: Add ConnectX-8 device to ifc Tariq Toukan
2024-12-04 22:09 ` [PATCH mlx5-next V5 03/11] net/mlx5: Add support for new scheduling elements Tariq Toukan
2024-12-04 22:09 ` [PATCH mlx5-next V5 04/11] net/mlx5: qos: Add ifc support for cross-esw scheduling Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 05/11] net/mlx5: DR, Expand SWS STE callbacks and consolidate common structs Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 06/11] net/mlx5: DR, Add support for ConnectX-8 steering Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 07/11] devlink: Extend devlink rate API with traffic classes bandwidth management Tariq Toukan
2024-12-07 2:10 ` Jakub Kicinski
2024-12-09 21:03 ` Tariq Toukan
2024-12-09 21:27 ` Jakub Kicinski
2025-01-20 11:55 ` Carolina Jubran
2025-01-20 18:14 ` Jakub Kicinski
2025-01-21 12:36 ` Carolina Jubran
2025-01-22 12:48 ` Carolina Jubran
2025-01-22 14:30 ` Jakub Kicinski
2025-02-05 6:22 ` Tariq Toukan
2025-02-05 6:56 ` Gal Pressman
2025-02-05 8:02 ` Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 08/11] net/mlx5: Add no-op implementation for setting tc-bw on rate objects Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 09/11] net/mlx5: Add support for setting tc-bw on nodes Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 10/11] net/mlx5: Add traffic class scheduling support for vport QoS Tariq Toukan
2024-12-04 22:09 ` [PATCH net-next V5 11/11] net/mlx5: Manage TC arbiter nodes and implement full support for tc-bw Tariq Toukan
2024-12-05 9:23 ` Leon Romanovsky [this message]
2024-12-07 2:13 ` [PATCH net-next V5 00/11] net/mlx5: ConnectX-8 SW Steering + Rate management on traffic classes Jakub Kicinski
2024-12-09 19:32 ` Tariq Toukan
2024-12-09 21:41 ` Jakub Kicinski
2024-12-11 9:49 ` Cosmin Ratiu
2024-12-12 1:49 ` Jakub Kicinski
2024-12-13 13:42 ` Cosmin Ratiu
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=20241205092355.GX1245331@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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