From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Dekel Peled <dekelp@mellanox.com>, dpdk-dev <dev@dpdk.org>,
Jerin Jacob <jerinjacobk@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Andrew Rybchenko <arybchenko@solarflare.com>,
maxime.coquelin@redhat.com,
Olivier Matz <olivier.matz@6wind.com>,
David Marchand <david.marchand@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce change in IPv6 item struct
Date: Thu, 6 Aug 2020 08:48:14 -0700 [thread overview]
Message-ID: <CACZ4nhsLenD5AvWUTgWiEDZXTS9NmK-zRGjGTdLWBX+tp=6uoQ@mail.gmail.com> (raw)
In-Reply-To: <4239474.pmar7NyoYS@thomas>
On Thu, Aug 6, 2020 at 5:30 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 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>
>
Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
next prev parent reply other threads:[~2020-08-06 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 19:51 Dekel Peled
2020-08-04 13:17 ` Dekel Peled
2020-08-06 17:09 ` Ori Kam
2020-08-06 12:30 ` Thomas Monjalon
2020-08-06 15:48 ` Ajit Khaparde [this message]
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='CACZ4nhsLenD5AvWUTgWiEDZXTS9NmK-zRGjGTdLWBX+tp=6uoQ@mail.gmail.com' \
--to=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 \
--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).