From: Ori Kam <orika@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce change in ETH and VLAN item structs
Date: Thu, 6 Aug 2020 17:07:17 +0000 [thread overview]
Message-ID: <AM6PR05MB51766A68FE5F9F5B382C6DF1DB480@AM6PR05MB5176.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <d7071384e8ac134037c6c6d3aa7a81809c4a3fa1.1596710789.git.dekelp@mellanox.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
>
> Structs rte_flow_item_eth and rte_flow_item_vlan will be modified,
> to include an additional value, indicating existence or absence of VLAN
> headers following the current header, as proposed in RFC
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpd
> k.org%2Farchives%2Fdev%2F2020-
> August%2F177536.html&data=02%7C01%7Corika%40mellanox.com%7Cb5
> 9964d529f14539086008d839f621db%7Ca652971c7d2e4d9ba6a4d149256f461b
> %7C0%7C0%7C637323076576373546&sdata=mWvf%2FeYiYhIXcoFaZMikx
> TqcJIS%2FxLQuNHGUqzcAf6w%3D&reserved=0.
> Because of ABI break this change is proposed for 20.11.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 5201142..2899f56 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -115,6 +115,11 @@ Deprecation Notices
> following the IPv6 header, as proposed in RFC
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpd
> k.org%2Farchives%2Fdev%2F2020-
> August%2F177257.html&data=02%7C01%7Corika%40mellanox.com%7Cb5
> 9964d529f14539086008d839f621db%7Ca652971c7d2e4d9ba6a4d149256f461b
> %7C0%7C0%7C637323076576373546&sdata=CR3%2B3iKBdLnGo4oRYy1ev
> MMsKxwVy%2Fzf6R44dQt2An8%3D&reserved=0.
>
> +* ethdev: The ``struct rte_flow_item_eth`` and ``struct rte_flow_item_vlan``
> + structs will be modified, to include an additional value, indicating existence
> + or absence of a VLAN header following the current header, as proposed in
> RFC
> +
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpd
> k.org%2Farchives%2Fdev%2F2020-
> August%2F177536.html&data=02%7C01%7Corika%40mellanox.com%7Cb5
> 9964d529f14539086008d839f621db%7Ca652971c7d2e4d9ba6a4d149256f461b
> %7C0%7C0%7C637323076576373546&sdata=mWvf%2FeYiYhIXcoFaZMikx
> TqcJIS%2FxLQuNHGUqzcAf6w%3D&reserved=0.
> +
> * traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly
> made
> ABI stable in the v19.11 release. The TM maintainer and other contributors
> have
> agreed to keep the TM APIs as experimental in expectation of additional spec
> --
> 1.8.3.1
Acked-by: Ori Kam <orika@mellanox.com>
Thanks,
Ori
prev parent reply other threads:[~2020-08-06 17:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 16:01 [dpdk-dev] [PATCH] doc: announce change in ETH item struct Dekel Peled
2020-08-05 3:39 ` Ajit Khaparde
2020-08-05 10:49 ` Andrew Rybchenko
2020-08-05 13:31 ` Dekel Peled
2020-08-05 13:44 ` Andrew Rybchenko
2020-08-05 14:25 ` Dekel Peled
2020-08-06 10:45 ` [dpdk-dev] [PATCH v2] doc: announce change in ETH and VLAN item structs Dekel Peled
2020-08-06 12:25 ` Thomas Monjalon
2020-08-06 15:14 ` Andrew Rybchenko
2020-08-06 15:50 ` Ajit Khaparde
2020-08-06 21:57 ` Thomas Monjalon
2020-08-06 17:07 ` Ori Kam [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=AM6PR05MB51766A68FE5F9F5B382C6DF1DB480@AM6PR05MB5176.eurprd05.prod.outlook.com \
--to=orika@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=asafp@mellanox.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 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).