From: Thomas Monjalon <thomas@monjalon.net>
To: Dekel Peled <dekelp@mellanox.com>
Cc: dev@dpdk.org, jerinjacobk@gmail.com, stephen@networkplumber.org,
arybchenko@solarflare.com, ajit.khaparde@broadcom.com,
maxime.coquelin@redhat.com, olivier.matz@6wind.com,
david.marchand@redhat.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce change in IPv6 item struct
Date: Thu, 06 Aug 2020 14:30:37 +0200 [thread overview]
Message-ID: <4239474.pmar7NyoYS@thomas> (raw)
In-Reply-To: <678a4cdeb67c9873c9d2842ec5a747f35600399f.1596483829.git.dekelp@mellanox.com>
03/08/2020 21:51, Dekel Peled:
> Struct rte_flow_item_ipv6 will be modified to include additional
> values, indicating existence or absence of IPv6 extension headers
> following the IPv6 header, as proposed in RFC
> https://mails.dpdk.org/archives/dev/2020-August/177257.html.
> Because of ABI break this change is proposed for 20.11.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---
> +* ethdev: The ``struct rte_flow_item_ipv6`` struct will be modified to include
> + additional values, indicating existence or absence of IPv6 extension headers
> + following the IPv6 header, as proposed in RFC
> + https://mails.dpdk.org/archives/dev/2020-August/177257.html.
That's the same idea as VLAN item, but for IPv6 extensions.
We need to address the issues of variable header parts with rte_flow, so
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2020-08-06 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 19:51 [dpdk-dev] [PATCH] doc: announce change in IPv6 item struct Dekel Peled
2020-08-04 13:17 ` Dekel Peled
2020-08-06 17:09 ` Ori Kam
2020-08-06 12:30 ` Thomas Monjalon [this message]
2020-08-06 15:48 ` Ajit Khaparde
2020-08-06 22:22 ` Thomas Monjalon
2020-08-06 15:10 ` Andrew Rybchenko
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=4239474.pmar7NyoYS@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.