DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michael Savisko <michaelsav@nvidia.com>
To: <orika@nvidia.com>, <andrew.rybchenko@oktetlabs.ru>,
	<ferruh.yigit@xilinx.com>
Cc: <dev@dpdk.org>, <michaelsav@nvidia.com>
Subject: [RFC] ethdev: add send to kernel action
Date: Thu, 11 Aug 2022 14:35:44 +0300	[thread overview]
Message-ID: <20220811113544.1718643-1-michaelsav@nvidia.com> (raw)

In some cases application may receive a packet that should have been
received by the kernel. In this case application uses KNI or other means
to transfer the packet to the kernel.
This commit introduces rte flow action that the application may use
to route the packet to the kernel while still in the HW.

Signed-off-by: Michael Savisko <michaelsav@nvidia.com>
---
 lib/librte_ethdev/rte_flow.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
index f92bef0184..969a607115 100644
--- a/lib/librte_ethdev/rte_flow.h
+++ b/lib/librte_ethdev/rte_flow.h
@@ -2853,6 +2853,11 @@ enum rte_flow_action_type {
 	 * See file rte_mtr.h for MTR profile object configuration.
 	 */
 	RTE_FLOW_ACTION_TYPE_METER_MARK,
+
+	/*
+	 * Send traffic to kernel.
+	 */
+	RTE_FLOW_ACTION_TYPE_SEND_TO_KERNEL,
 };
 
 /**
-- 
2.27.0


             reply	other threads:[~2022-08-11 11:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 11:35 Michael Savisko [this message]
2022-08-15 12:02 ` Ori Kam
2022-08-16  9:50 ` Ferruh Yigit
2022-09-12 13:32   ` Thomas Monjalon
2022-09-12 13:39     ` Michael Savisko
2022-09-12 14:41       ` Andrew Rybchenko
2022-09-13 12:09         ` Michael Savisko
2022-09-14  9:57           ` Thomas Monjalon
2022-09-14  9:32 ` [PATCH v2] " Michael Savisko
2022-09-19 15:50   ` [PATCH v3] " Michael Savisko
2022-09-20 11:08     ` Ori Kam
2022-09-26 13:06     ` Andrew Rybchenko
2022-09-28 14:30       ` Michael Savisko
2022-09-29 14:54     ` [PATCH v4] " Michael Savisko
2022-10-03  7:53       ` Andrew Rybchenko
2022-10-03  8:23         ` Ori Kam
2022-10-03  9:44           ` Andrew Rybchenko
2022-10-03  9:57             ` Ori Kam
2022-10-03 10:47               ` Andrew Rybchenko
2022-10-03 11:06                 ` Ori Kam
2022-10-03 11:08                   ` Andrew Rybchenko
2022-10-03 16:34       ` [PATCH v5] " Michael Savisko
2022-10-04  7:48         ` Andrew Rybchenko
2022-09-20 10:57   ` [PATCH v2] " Ori Kam

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=20220811113544.1718643-1-michaelsav@nvidia.com \
    --to=michaelsav@nvidia.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.com \
    --cc=orika@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).