From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: [PATCH v3 0/3] net/mlx5: support jump FDB Rx
Date: Wed, 26 Feb 2025 17:04:22 +0100 [thread overview]
Message-ID: <20250226160425.78147-1-dsosnowski@nvidia.com> (raw)
In-Reply-To: <20250226140119.2142352-1-suanmingm@nvidia.com>
Before FW introduced the JUMP_FDB_RX action feature, jump from
FDB Tx to Rx is not allowed. JUMP_FDB_RX feature introduces
the internal loopback for Tx case and allow the REG C0 C1 B be
preserved as well.
This series adds the jump from FDB Tx to FDB Rx support and allows
RSS action in FDB domain rule when jump FDB Rx is supported.
v3:
- Rebased on v2 of mlx5 Unified FDB patches (series 34723)
Suanming Mou (3):
net/mlx5/hws: support jump FDB Rx
net/mlx5: add jump FDB Rx flag
net/mlx5: allow FDB RSS
doc/guides/nics/mlx5.rst | 4 ++++
drivers/common/mlx5/mlx5_devx_cmds.c | 8 +++++++
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/common/mlx5/mlx5_prm.h | 9 +++++++-
drivers/net/mlx5/hws/mlx5dr_action.c | 26 +++++++++++++++++-----
drivers/net/mlx5/hws/mlx5dr_action.h | 4 ++++
drivers/net/mlx5/hws/mlx5dr_cmd.c | 9 ++++++++
drivers/net/mlx5/hws/mlx5dr_cmd.h | 2 ++
drivers/net/mlx5/hws/mlx5dr_context.c | 17 ++++++++++++++
drivers/net/mlx5/hws/mlx5dr_context.h | 2 ++
drivers/net/mlx5/linux/mlx5_os.c | 9 ++++++--
drivers/net/mlx5/mlx5.h | 1 +
drivers/net/mlx5/mlx5_flow.c | 4 ++--
drivers/net/mlx5/mlx5_flow_dv.c | 32 ++++++++++++++-------------
drivers/net/mlx5/mlx5_flow_hw.c | 28 ++++++++++++++++++-----
15 files changed, 125 insertions(+), 31 deletions(-)
--
2.39.5
next prev parent reply other threads:[~2025-02-26 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 0:45 [PATCH " Suanming Mou
2025-02-25 0:45 ` [PATCH 1/3] net/mlx5/hws: " Suanming Mou
2025-02-26 10:28 ` Bing Zhao
2025-02-26 13:31 ` Suanming Mou
2025-02-25 0:45 ` [PATCH 2/3] net/mlx5: add jump FDB Rx flag Suanming Mou
2025-02-26 10:37 ` Bing Zhao
2025-02-26 13:36 ` Suanming Mou
2025-02-25 0:45 ` [PATCH 3/3] net/mlx5: allow FDB RSS Suanming Mou
2025-02-26 10:49 ` Bing Zhao
2025-02-26 13:43 ` Suanming Mou
2025-02-26 14:00 ` Bing Zhao
2025-02-26 14:01 ` [PATCH v2 0/3] net/mlx5: support jump FDB Rx Suanming Mou
2025-02-26 14:01 ` [PATCH v2 1/3] net/mlx5/hws: " Suanming Mou
2025-02-26 18:12 ` Bing Zhao
2025-02-26 14:01 ` [PATCH v2 2/3] net/mlx5: add jump FDB Rx flag Suanming Mou
2025-02-26 14:01 ` [PATCH v2 3/3] net/mlx5: allow FDB RSS Suanming Mou
2025-02-26 16:04 ` Dariusz Sosnowski [this message]
2025-02-26 16:04 ` [PATCH v3 1/3] net/mlx5/hws: support jump FDB Rx Dariusz Sosnowski
2025-02-26 16:04 ` [PATCH v3 2/3] net/mlx5: add jump FDB Rx flag Dariusz Sosnowski
2025-02-26 16:04 ` [PATCH v3 3/3] net/mlx5: allow FDB RSS Dariusz Sosnowski
2025-02-26 16:53 ` [PATCH v3 0/3] net/mlx5: support jump FDB Rx Raslan Darawsheh
2025-02-26 18:13 ` Bing Zhao
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=20250226160425.78147-1-dsosnowski@nvidia.com \
--to=dsosnowski@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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).