From: Jiawei Wang <jiaweiw@nvidia.com>
To: <suanmingm@nvidia.com>, <orika@nvidia.com>, <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH 0/3] net/mlx5: extend send to kernel action support
Date: Fri, 8 Sep 2023 12:20:57 +0300 [thread overview]
Message-ID: <20230908092100.38587-1-jiaweiw@nvidia.com> (raw)
The send to kernel action was supported in NIC and FDB tables,
Currently[1], the send to kernel action is created in NIC RX only.
With some TC rules (example: roce packets, redirects into rep ports)
and DPDK RTE rules for the rest of the traffic. Then it needs the
specific rule to re-route the packets into the kernel through the FDB
table.
This patchset adds the FDB and NIC-TX tables support for sending to the kernel
action, also updates the documentation.
[1]
https://patchwork.dpdk.org/project/dpdk/list/?series=25318
Jiawei Wang (3):
net/mlx5: extend send to kernel action support
net/mlx5: extend hws send to kernel action support
doc: adds the description for send to kernel
doc/guides/nics/mlx5.rst | 7 +++++
doc/guides/prog_guide/rte_flow.rst | 9 ++++++
drivers/net/mlx5/linux/mlx5_os.c | 25 ++++++++++-------
drivers/net/mlx5/mlx5.h | 6 ++--
drivers/net/mlx5/mlx5_flow.h | 1 +
drivers/net/mlx5/mlx5_flow_dv.c | 17 +++++++----
drivers/net/mlx5/mlx5_flow_hw.c | 45 +++++++++++++++++++++---------
lib/ethdev/rte_flow.h | 1 -
8 files changed, 79 insertions(+), 32 deletions(-)
--
2.18.1
next reply other threads:[~2023-09-08 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 9:20 Jiawei Wang [this message]
2023-09-08 9:20 ` [PATCH 1/3] " Jiawei Wang
2023-09-08 9:35 ` Suanming Mou
2023-09-18 12:52 ` Raslan Darawsheh
2023-09-08 9:20 ` [PATCH 2/3] net/mlx5: extend hws " Jiawei Wang
2023-09-08 9:35 ` Suanming Mou
2023-09-08 9:21 ` [PATCH 3/3] doc: adds the description for send to kernel Jiawei Wang
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=20230908092100.38587-1-jiaweiw@nvidia.com \
--to=jiaweiw@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
/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).