From: "Jonas Pfefferle" <pepperjo@japf.ch>
To: "Anatoly Burakov" <anatoly.burakov@intel.com>, dev@dpdk.org
Cc: "Neil Horman" <nhorman@tuxdriver.com>,
"John McNamara" <john.mcnamara@intel.com>,
"Marko Kovacevic" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice for memory hotplug changes
Date: Mon, 12 Feb 2018 16:58:39 +0100 [thread overview]
Message-ID: <ximss-45127252@switchplus-mail.ch> (raw)
In-Reply-To: <32a6f11b2e6bc88c90ef39cb0494b8c3335a94d7.1516270352.git.anatoly.burakov@intel.com>
On Thu, 18 Jan 2018 10:32:28 +0000
Anatoly Burakov <anatoly.burakov@intel.com> wrote:
> Due to coming changes outlined in memory hotplug RFC, there will
> be several API/ABI changes.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>
> Notes:
> Patch outlining future changes:
> http://dpdk.org/dev/patchwork/patch/32467/
>
> v2: added rte_mem_config and rte_memzone changes to the
>announcement
>
> doc/guides/rel_notes/deprecation.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
>b/doc/guides/rel_notes/deprecation.rst
> index 13e8543..93cbeea 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -8,6 +8,15 @@ API and ABI deprecation notices are to be posted
>here.
> Deprecation Notices
> -------------------
>
> +* eal: due to internal data layoyut reorganization, there will be
>changes to
> + several structures and functions as a result of coming changes to
>support
> + memory hotplug in v18.05.
> + ``rte_eal_get_physmem_layout`` will be deprecated and removed in
>subsequent
> + releases.
> + ``rte_mem_config`` contents will change due to switch to memseg
>lists.
> + ``rte_memzone`` member ``memseg_id`` will no longer serve any
>useful purpose
> + and will be removed.
> +
> * 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
Acked-by: Jonas Pfefferle <pepperjo@japf.ch>
next prev parent reply other threads:[~2018-02-12 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:17 [dpdk-dev] [PATCH] doc: add deprecation notice for physmem layout function Anatoly Burakov
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 [this message]
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=ximss-45127252@switchplus-mail.ch \
--to=pepperjo@japf.ch \
--cc=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).