From: Jerin Jacob <jerinjacobk@gmail.com>
To: Satheesh Paul <psatheesh@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/cnxk: support IPv6 fragment flow pattern item
Date: Mon, 9 May 2022 18:07:52 +0530 [thread overview]
Message-ID: <CALBAE1NVS0611PetbBZbhRD7UyOVuXKgomrEXiJyzxuOP2EVyw@mail.gmail.com> (raw)
In-Reply-To: <20220427062320.424570-2-psatheesh@marvell.com>
On Wed, Apr 27, 2022 at 11:53 AM <psatheesh@marvell.com> wrote:
>
> From: Satheesh Paul <psatheesh@marvell.com>
>
> Support matching IPv6 fragment extension header
> with RTE_FLOW_ITEM_TYPE_IPV6_FRAG_EXT flow pattern item.
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Series applied to dpdk-next-net-mrvl/for-next-net. Thanks
> ---
> doc/guides/nics/features/cnxk.ini | 1 +
> doc/guides/nics/features/cnxk_vec.ini | 1 +
> doc/guides/nics/features/cnxk_vf.ini | 1 +
> drivers/net/cnxk/cnxk_flow.c | 3 +++
> 4 files changed, 6 insertions(+)
>
> diff --git a/doc/guides/nics/features/cnxk.ini b/doc/guides/nics/features/cnxk.ini
> index 7cac8beb61..1876fe86c7 100644
> --- a/doc/guides/nics/features/cnxk.ini
> +++ b/doc/guides/nics/features/cnxk.ini
> @@ -65,6 +65,7 @@ icmp = Y
> ipv4 = Y
> ipv6 = Y
> ipv6_ext = Y
> +ipv6_frag_ext = Y
> mark = Y
> mpls = Y
> nvgre = Y
> diff --git a/doc/guides/nics/features/cnxk_vec.ini b/doc/guides/nics/features/cnxk_vec.ini
> index 0803bb3c29..5d0976e6ce 100644
> --- a/doc/guides/nics/features/cnxk_vec.ini
> +++ b/doc/guides/nics/features/cnxk_vec.ini
> @@ -61,6 +61,7 @@ icmp = Y
> ipv4 = Y
> ipv6 = Y
> ipv6_ext = Y
> +ipv6_frag_ext = Y
> mark = Y
> mpls = Y
> nvgre = Y
> diff --git a/doc/guides/nics/features/cnxk_vf.ini b/doc/guides/nics/features/cnxk_vf.ini
> index ed3e231c5f..c4ee32a9ad 100644
> --- a/doc/guides/nics/features/cnxk_vf.ini
> +++ b/doc/guides/nics/features/cnxk_vf.ini
> @@ -57,6 +57,7 @@ icmp = Y
> ipv4 = Y
> ipv6 = Y
> ipv6_ext = Y
> +ipv6_frag_ext = Y
> mark = Y
> mpls = Y
> nvgre = Y
> diff --git a/drivers/net/cnxk/cnxk_flow.c b/drivers/net/cnxk/cnxk_flow.c
> index ff962c141d..34f5d54f28 100644
> --- a/drivers/net/cnxk/cnxk_flow.c
> +++ b/drivers/net/cnxk/cnxk_flow.c
> @@ -14,6 +14,9 @@ const struct cnxk_rte_flow_term_info term[] = {
> sizeof(struct rte_flow_item_ipv4)},
> [RTE_FLOW_ITEM_TYPE_IPV6] = {ROC_NPC_ITEM_TYPE_IPV6,
> sizeof(struct rte_flow_item_ipv6)},
> + [RTE_FLOW_ITEM_TYPE_IPV6_FRAG_EXT] = {
> + ROC_NPC_ITEM_TYPE_IPV6_FRAG_EXT,
> + sizeof(struct rte_flow_item_ipv6_frag_ext)},
> [RTE_FLOW_ITEM_TYPE_ARP_ETH_IPV4] = {
> ROC_NPC_ITEM_TYPE_ARP_ETH_IPV4,
> sizeof(struct rte_flow_item_arp_eth_ipv4)},
> --
> 2.25.4
>
prev parent reply other threads:[~2022-05-09 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:23 [dpdk-dev] [PATCH 1/2] common/cnxk: " psatheesh
2022-04-27 6:23 ` [dpdk-dev] [PATCH 2/2] net/cnxk: " psatheesh
2022-05-09 12:37 ` Jerin Jacob [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=CALBAE1NVS0611PetbBZbhRD7UyOVuXKgomrEXiJyzxuOP2EVyw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).