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 3/3] doc: adds the description for send to kernel
Date: Fri, 8 Sep 2023 12:21:00 +0300 [thread overview]
Message-ID: <20230908092100.38587-4-jiaweiw@nvidia.com> (raw)
In-Reply-To: <20230908092100.38587-1-jiaweiw@nvidia.com>
This patch adds the description for send to kernel action support.
Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
---
doc/guides/nics/mlx5.rst | 7 +++++++
doc/guides/prog_guide/rte_flow.rst | 9 +++++++++
lib/ethdev/rte_flow.h | 1 -
3 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index eac67a7864..7bee57d9dd 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -165,6 +165,7 @@ Features
- Sub-Function.
- Matching on represented port.
- Matching on aggregated affinity.
+- Send to kernel.
Limitations
@@ -720,6 +721,12 @@ Limitations
The flow engine of a process cannot move from active to standby mode
if preceding active application rules are still present and vice versa.
+- Send to kernel action (``RTE_FLOW_ACTION_TYPE_SEND_TO_KERNEL``):
+
+ - Supports on non-root table.
+ - Supports on isolated mode.
+ - In HW steering (``dv_flow_en`` = 2):
+ - not supported on guest port.
Statistics
----------
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 5bc998a433..f8c130bc8b 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -3490,6 +3490,15 @@ The ``quota`` value is reduced according to ``mode`` setting.
| ``RTE_FLOW_QUOTA_MODE_L3`` | Count packet bytes starting from L3 |
+------------------+----------------------------------------------------+
+Action: ``SEND_TO_KERNEL``
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Send packets to the kernel, without going to userspace at all.
+
+The packets will be received by the kernel driver sharing the
+same device as the DPDK port on which this action is configured.
+
+
Negative types
~~~~~~~~~~~~~~
diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
index 2ebb76dbc0..23addb4382 100644
--- a/lib/ethdev/rte_flow.h
+++ b/lib/ethdev/rte_flow.h
@@ -2931,7 +2931,6 @@ enum rte_flow_action_type {
* The packets will be received by the kernel driver sharing
* the same device as the DPDK port on which this action is configured.
* This action mostly suits bifurcated driver model.
- * This is an ingress non-transfer action only.
*
* No associated configuration structure.
*/
--
2.18.1
prev parent 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 [PATCH 0/3] net/mlx5: extend send to kernel action support Jiawei Wang
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 ` Jiawei Wang [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=20230908092100.38587-4-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).