From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, stephen@networkplumber.org,
olivier.matz@6wind.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] doc: deprecation notice for change of ether struct alignment
Date: Tue, 9 Jul 2019 15:58:36 +0100 [thread overview]
Message-ID: <20190709145836.43493-1-bruce.richardson@intel.com> (raw)
The ethernet address structure alignment will be changed to 2B alignment in
19.11. Flag this to users.
Impact is expected to be minimal for this change since ethernet addresses
are generally 2B aligned anyway.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.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 a7796f49b..7a04b9b09 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -11,6 +11,11 @@ API and ABI deprecation notices are to be posted here.
Deprecation Notices
-------------------
+* net: The alignment of the ethernet address structure in DPDK,
+ ``rte_ether_addr`` will be increased to two, i.e. 16-bit aligned, in the
+ 19.11 release. This will only affect any data structures where an ethernet
+ address is currently aligned on a single byte boundary.
+
* meson: The minimum supported version of meson for configuring and building
DPDK will be increased to v0.47.1 (from 0.41) from DPDK 19.05 onwards. For
those users with a version earlier than 0.47.1, an updated copy of meson
--
2.21.0
next reply other threads:[~2019-07-09 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 14:58 Bruce Richardson [this message]
2019-07-09 14:59 ` Stephen Hemminger
2019-07-09 15:02 ` Bruce Richardson
2019-07-18 22:09 ` [dpdk-dev] [PATCH] doc: add deprecation notice about changes to ethernet structures Stephen Hemminger
2019-07-19 10:57 ` Bruce Richardson
2019-07-19 16:56 ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2019-07-23 11:28 ` Andrew Rybchenko
2019-07-31 10:46 ` Ferruh Yigit
2019-08-06 11:26 ` Thomas Monjalon
2019-08-10 20:22 ` Thomas Monjalon
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=20190709145836.43493-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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).