From: <psatheesh@marvell.com>
To: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>
Cc: <dev@dpdk.org>, Satheesh Paul <psatheesh@marvell.com>
Subject: [dpdk-dev] [PATCH 1/2] common/cnxk: support IPv6 fragment flow pattern item
Date: Wed, 27 Apr 2022 11:53:19 +0530 [thread overview]
Message-ID: <20220427062320.424570-1-psatheesh@marvell.com> (raw)
From: Satheesh Paul <psatheesh@marvell.com>
ROC changes to support RTE_FLOW_ITEM_TYPE_IPV6_FRAG_EXT
flow pattern item.
Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
---
drivers/common/cnxk/roc_npc.h | 1 +
drivers/common/cnxk/roc_npc_parse.c | 7 +++++++
2 files changed, 8 insertions(+)
diff --git a/drivers/common/cnxk/roc_npc.h b/drivers/common/cnxk/roc_npc.h
index 723eadc649..3ba8a181df 100644
--- a/drivers/common/cnxk/roc_npc.h
+++ b/drivers/common/cnxk/roc_npc.h
@@ -15,6 +15,7 @@ enum roc_npc_item_type {
ROC_NPC_ITEM_TYPE_E_TAG,
ROC_NPC_ITEM_TYPE_IPV4,
ROC_NPC_ITEM_TYPE_IPV6,
+ ROC_NPC_ITEM_TYPE_IPV6_FRAG_EXT,
ROC_NPC_ITEM_TYPE_ARP_ETH_IPV4,
ROC_NPC_ITEM_TYPE_MPLS,
ROC_NPC_ITEM_TYPE_ICMP,
diff --git a/drivers/common/cnxk/roc_npc_parse.c b/drivers/common/cnxk/roc_npc_parse.c
index 1ce0dadfef..0748646779 100644
--- a/drivers/common/cnxk/roc_npc_parse.c
+++ b/drivers/common/cnxk/roc_npc_parse.c
@@ -594,6 +594,13 @@ npc_parse_lc(struct npc_parse_state *pst)
info.len = pst->pattern->size;
info.hw_hdr_len = 40;
break;
+ case ROC_NPC_ITEM_TYPE_IPV6_FRAG_EXT:
+ lid = NPC_LID_LC;
+ lt = NPC_LT_LC_IP6_EXT;
+ flags = NPC_F_LC_U_IP6_FRAG;
+ info.len = pst->pattern->size;
+ info.hw_hdr_len = 40;
+ break;
case ROC_NPC_ITEM_TYPE_L3_CUSTOM:
lt = NPC_LT_LC_CUSTOM0;
info.len = pst->pattern->size;
--
2.25.4
next reply other threads:[~2022-04-27 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:23 psatheesh [this message]
2022-04-27 6:23 ` [dpdk-dev] [PATCH 2/2] net/cnxk: " psatheesh
2022-05-09 12:37 ` Jerin Jacob
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=20220427062320.424570-1-psatheesh@marvell.com \
--to=psatheesh@marvell.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).