From: Yongseok Koh <yskoh@mellanox.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"keith.wiles@intel.com" <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice on external memory support
Date: Thu, 2 Aug 2018 05:58:14 +0000 [thread overview]
Message-ID: <71DD2117-A90A-4DD8-AA16-391224CC8C89@mellanox.com> (raw)
In-Reply-To: <12c37dfc8dda4acbd7b49b00a577c3a9f5cbfbba.1533125146.git.anatoly.burakov@intel.com>
> On Aug 1, 2018, at 5:07 AM, Anatoly Burakov <anatoly.burakov@intel.com> wrote:
>
> Due to the upcoming external memory support [1], some API and ABI
> changes will be required. In addition, although the changes called
> out in the deprecation notice are not yet present in form of code
> in the published RFC itself, they are based on consensus on the
> mailing list [2] on how to best implement this feature.
>
> [1] https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpatches.dpdk.org%2Fproject%2Fdpdk%2Flist%2F%3Fseries%3D453%26state%3D*&data=02%7C01%7Cyskoh%40mellanox.com%7Cc4caf7979dd943bb48c508d5f7a7661f%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636687220727753880&sdata=9yDGZf21ImYOUzM85n92cs%2BsgeafrrhG%2FlmJpWVpcWA%3D&reserved=0
> [2] https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmails.dpdk.org%2Farchives%2Fdev%2F2018-July%2F108002.html&data=02%7C01%7Cyskoh%40mellanox.com%7Cc4caf7979dd943bb48c508d5f7a7661f%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636687220727753880&sdata=zn4ZfXModNRgnSp649JFWd4Byr7RxH8mgcM6IKJTGWk%3D&reserved=0
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 14714fe94..629154711 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -8,6 +8,21 @@ API and ABI deprecation notices are to be posted here.
> Deprecation Notices
> -------------------
>
> +* eal: certain structures will change in EAL on account of upcoming external
> + memory support. Aside from internal changes leading to an ABI break, the
> + following externally visible changes will also be implemented:
> +
> + - ``rte_memseg_list`` will change to include a boolean flag indicating
> + whether a particular memseg list is externally allocated. This will have
> + implications for any users of memseg-walk-related functions, as they will
> + now have to skip externally allocated segments in most cases if the intent
> + is to only iterate over internal DPDK memory.
> + - ``socket_id`` parameter across the entire DPDK will gain additional meaning,
> + as some socket ID's will now be representing externally allocated memory. No
> + changes will be required for existing code as backwards compatibility will
> + be kept, and those who do not use this feature will not see these extra
> + socket ID's.
> +
> * eal: both declaring and identifying devices will be streamlined in v18.08.
> New functions will appear to query a specific port from buses, classes of
> device and device drivers. Device declaration will be made coherent with the
> --
Acked-by: Yongseok Koh <yskoh@mellanox.com>
Thanks
next prev parent reply other threads:[~2018-08-02 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 12:07 Anatoly Burakov
2018-08-01 12:20 ` Wiles, Keith
2018-08-02 2:37 ` Wang, Zhihong
2018-08-02 3:38 ` Jerin Jacob
2018-08-02 5:58 ` Yongseok Koh [this message]
2018-08-02 7:56 ` Maxime Coquelin
2018-08-02 9:25 ` Shreyansh Jain
2018-08-05 23:41 ` 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=71DD2117-A90A-4DD8-AA16-391224CC8C89@mellanox.com \
--to=yskoh@mellanox.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--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).