From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wiles, Keith" Subject: Re: [PATCH] doc: add deprecation notice on external memory support Date: Wed, 1 Aug 2018 12:20:51 +0000 Message-ID: References: <12c37dfc8dda4acbd7b49b00a577c3a9f5cbfbba.1533125146.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , Neil Horman , "Mcnamara, John" , "Kovacevic, Marko" , "thomas@monjalon.net" To: "Burakov, Anatoly" Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id B94F15F2B for ; Wed, 1 Aug 2018 14:21:02 +0200 (CEST) In-Reply-To: <12c37dfc8dda4acbd7b49b00a577c3a9f5cbfbba.1533125146.git.anatoly.burakov@intel.com> Content-Language: en-US Content-ID: <1D156E06B7E8134593EF11C61C124E84@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > On Aug 1, 2018, at 7:07 AM, Burakov, Anatoly = wrote: >=20 > 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. >=20 > [1] http://patches.dpdk.org/project/dpdk/list/?series=3D453&state=3D* > [2] https://mails.dpdk.org/archives/dev/2018-July/108002.html >=20 > Signed-off-by: Anatoly Burakov > --- > doc/guides/rel_notes/deprecation.rst | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) >=20 > 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 > ------------------- >=20 > +* eal: certain structures will change in EAL on account of upcoming exte= rnal > + memory support. Aside from internal changes leading to an ABI break, t= he > + 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 me= mory. No > + changes will be required for existing code as backwards compatibilit= y will > + be kept, and those who do not use this feature will not see these ex= tra > + 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 wit= h the Acked-by: Keith Wiles > --=20 > 2.17.1 Regards, Keith