From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add deprecation notice for physmem layout function
Date: Wed, 17 Jan 2018 17:17:15 +0000 [thread overview]
Message-ID: <c23b5df92836eff343ea6af532fabb8529914b6f.1516208579.git.anatoly.burakov@intel.com> (raw)
Due to coming changes outlined in memory hotplug RFC, that
function will no longer serve any meaningful purpose.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
Notes:
Patch outlining future changes:
http://dpdk.org/dev/patchwork/patch/32467/
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 13e8543..28f217d 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -8,6 +8,10 @@ API and ABI deprecation notices are to be posted here.
Deprecation Notices
-------------------
+* eal: due to internal data layoyut reorganization, function
+ ``rte_eal_get_physmem_layout`` will be deprecated in v18.05 and removed in
+ subsequent releases.
+
* eal: several API and ABI changes are planned for ``rte_devargs`` in v18.02.
The format of device command line parameters will change. The bus will need
to be explicitly stated in the device declaration. The enum ``rte_devtype``
--
2.7.4
next reply other threads:[~2018-01-17 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:17 Anatoly Burakov [this message]
2018-01-18 9:55 ` Burakov, Anatoly
2018-01-18 10:32 ` [dpdk-dev] [PATCH v2] doc: add deprecation notice for memory hotplug changes Anatoly Burakov
2018-01-23 10:36 ` Mcnamara, John
2018-02-05 11:47 ` Bruce Richardson
2018-02-07 10:11 ` Jerin Jacob
2018-02-14 14:48 ` Thomas Monjalon
2018-02-12 15:58 ` Jonas Pfefferle
2018-02-13 0:24 ` Yongseok Koh
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=c23b5df92836eff343ea6af532fabb8529914b6f.1516208579.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.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).