From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Patrisious Haddad <phaddad@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH rdma-next 0/2] Add multiple priorities support to mlx5 RDMA TRANSPORT tables
Date: Tue, 17 Jun 2025 11:19:14 +0300 [thread overview]
Message-ID: <cover.1750148083.git.leon@kernel.org> (raw)
Hi,
This short series from Patrisious extends mlx5 flow steering logic to
allow creation rule creation with priorities in RDMA TRANSPORT tables.
Thanks
Patrisious Haddad (2):
net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain
RDMA/mlx5: Add multiple priorities support to RDMA TRANSPORT userspace
tables
drivers/infiniband/hw/mlx5/fs.c | 40 ++++++++++++-------
drivers/infiniband/hw/mlx5/fs.h | 8 +++-
drivers/infiniband/hw/mlx5/mlx5_ib.h | 4 +-
.../net/ethernet/mellanox/mlx5/core/fs_core.c | 30 ++++++++++----
include/linux/mlx5/fs.h | 2 +-
5 files changed, 56 insertions(+), 28 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-17 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 8:19 Leon Romanovsky [this message]
2025-06-17 8:19 ` [PATCH mlx5-next 1/2] net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain Leon Romanovsky
2025-06-25 23:42 ` Jakub Kicinski
2025-06-26 6:49 ` Leon Romanovsky
2025-06-17 8:19 ` [PATCH rdma-next 2/2] RDMA/mlx5: Add multiple priorities support to RDMA TRANSPORT userspace tables Leon Romanovsky
2025-06-18 4:53 ` [PATCH rdma-next 0/2] Add multiple priorities support to mlx5 RDMA TRANSPORT tables Zhu Yanjun
2025-06-18 10:39 ` Leon Romanovsky
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=cover.1750148083.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.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 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.