From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, "Doherty, Declan" <declan.doherty@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
"John Daley (johndale)" <johndale@cisco.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v1 4/4] doc: announce API change for flow VLAN pattern item
Date: Wed, 14 Feb 2018 16:37:35 +0100 [thread overview]
Message-ID: <20180214152847.19774-5-adrien.mazarguil@6wind.com> (raw)
In-Reply-To: <20180214152847.19774-1-adrien.mazarguil@6wind.com>
This will finally bring consistency to the VLAN pattern item definition,
particularly when attempting to match QinQ traffic. Applications relying on
TCI and no QinQ shouldn't notice a difference.
On the other hand, applications relying on EtherType matching will have to
adapt their patterns so they match from outermost to innermost (as on the
wire) instead of the current mess (innermost, then outermost to innermost
in case of QinQ).
Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.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 77390ce9f..5cd337807 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -77,3 +77,8 @@ Deprecation Notices
``struct rte_flow_item_raw`` will be replaced by standard pointers to the
same data. They proved difficult to use in the field (e.g. no possibility
of static initialization) and are unsuitable for C++ applications.
+
+* rte_flow: VLAN pattern item (``struct rte_flow_item_vlan``) will be
+ redefined more logically with TCI followed by inner EtherType (wire order)
+ instead of outer TPID followed by TCI (with inner EtherType part of the
+ previous pattern item), as the latter results in much confusion.
--
2.11.0
next prev parent reply other threads:[~2018-02-14 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:37 [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 1/4] doc: announce API change for flow actions Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 2/4] doc: announce API change for flow RSS action Adrien Mazarguil
2018-02-14 15:37 ` [dpdk-dev] [PATCH v1 3/4] doc: announce API change for flow RSS/RAW actions Adrien Mazarguil
2018-02-14 15:37 ` Adrien Mazarguil [this message]
2018-02-14 15:55 ` [dpdk-dev] [PATCH v1 0/4] doc: announce API changes for flow rules Nélio Laranjeiro
2018-02-14 16:06 ` 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=20180214152847.19774-5-adrien.mazarguil@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=nhorman@tuxdriver.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@mellanox.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).