DPDK patches and discussions
 help / color / mirror / Atom feed
From: simei <simei.su@intel.com>
To: qi.z.zhang@intel.com, jingjing.wu@intel.com,
	beilei.xing@intel.com, qiming.yang@intel.com
Cc: dev@dpdk.org, simei.su@intel.com
Subject: [dpdk-dev] [RFC] ethdev: support input set change by RSS action
Date: Thu,  4 Jul 2019 12:47:09 +0800	[thread overview]
Message-ID: <1562215629-75520-1-git-send-email-simei.su@intel.com> (raw)

From: Simei Su <simei.su@intel.com>

This RFC introduces inputset structure to rte_flow_action_rss to
support input set specific configuration by rte_flow RSS action.

We can give an testpmd command line example to make it more clear.

For example, below flow selects the l4 port as inputset for any
eth/ipv4/tcp packet: #flow create 0 ingress pattern eth / ipv4 / tcp /
end actions rss inputset tcp src mask 0xffff dst mask 0xffff /end

Signed-off-by: Simei Su <simei.su@intel.com>
---
 lib/librte_ethdev/rte_flow.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/lib/librte_ethdev/rte_flow.h b/lib/librte_ethdev/rte_flow.h
index f3a8fb1..2a455b6 100644
--- a/lib/librte_ethdev/rte_flow.h
+++ b/lib/librte_ethdev/rte_flow.h
@@ -1796,6 +1796,9 @@ struct rte_flow_action_rss {
 	uint32_t queue_num; /**< Number of entries in @p queue. */
 	const uint8_t *key; /**< Hash key. */
 	const uint16_t *queue; /**< Queue indices to use. */
+	struct rte_flow_item *inputset; /** Provide more specific inputset configuration.
+					 * ignore spec, only mask.
+					 */
 };
 
 /**
-- 
1.8.3.1


             reply	other threads:[~2019-07-04  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  4:47 simei [this message]
2019-07-04  9:07 ` Adrien Mazarguil
2019-07-04 13:55   ` Zhang, Qi Z
2019-07-04 14:08     ` Adrien Mazarguil
2019-07-09  5:41       ` Zhang, Qi Z
2019-07-09  8:19         ` Jerin Jacob Kollanukkaran

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=1562215629-75520-1-git-send-email-simei.su@intel.com \
    --to=simei.su@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.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).