From: Simei Su <simei.su@intel.com>
To: ferruh.yigit@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, junfeng.guo@intel.com, yahui.cao@intel.com,
xiao.zhang@intel.com, Simei Su <simei.su@intel.com>
Subject: [dpdk-dev] [PATCH v2 1/2] ethdev: add eCPRI RSS offload types
Date: Wed, 18 Nov 2020 09:34:48 +0800 [thread overview]
Message-ID: <20201118013449.106762-2-simei.su@intel.com> (raw)
In-Reply-To: <20201118013449.106762-1-simei.su@intel.com>
This patch defines new RSS offload types for eCPRI. For eCPRI with
Message Type 0, the hash field is physical channel ID.
Signed-off-by: Simei Su <simei.su@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
lib/librte_ethdev/rte_ethdev.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
index 69fc973..f5f8919 100644
--- a/lib/librte_ethdev/rte_ethdev.h
+++ b/lib/librte_ethdev/rte_ethdev.h
@@ -525,6 +525,7 @@ struct rte_eth_rss_conf {
#define ETH_RSS_L2TPV3 (1ULL << 29)
#define ETH_RSS_PFCP (1ULL << 30)
#define ETH_RSS_PPPOE (1ULL << 31)
+#define ETH_RSS_ECPRI (1ULL << 32)
/*
* We use the following macros to combine with above ETH_RSS_* for
--
2.9.5
next prev parent reply other threads:[~2020-11-18 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 5:32 [dpdk-dev] [PATCH v1 0/2] extend " Simei Su
2020-11-16 5:32 ` [dpdk-dev] [PATCH v1 1/2] ethdev: add eCPRI " Simei Su
2020-11-17 13:06 ` Ferruh Yigit
2020-11-16 5:32 ` [dpdk-dev] [PATCH v1 2/2] app/testpmd: support extended " Simei Su
2020-11-17 13:11 ` Ferruh Yigit
2020-11-18 1:34 ` [dpdk-dev] [PATCH v2 0/2] extend " Simei Su
2020-11-18 1:34 ` Simei Su [this message]
2020-11-18 1:34 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: support extended " Simei Su
2020-11-18 12:55 ` Ferruh Yigit
2020-11-18 12:56 ` [dpdk-dev] [PATCH v2 0/2] extend " Ferruh Yigit
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=20201118013449.106762-2-simei.su@intel.com \
--to=simei.su@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=xiao.zhang@intel.com \
--cc=yahui.cao@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).