From patchwork Wed Aug 1 12:07:16 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Anatoly Burakov X-Patchwork-Id: 43502 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7C8575F29; Wed, 1 Aug 2018 14:07:46 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 43FCA5F21 for ; Wed, 1 Aug 2018 14:07:44 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2018 05:07:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,431,1526367600"; d="scan'208";a="69209502" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by FMSMGA003.fm.intel.com with ESMTP; 01 Aug 2018 05:07:22 -0700 Received: from sivswdev01.ir.intel.com (sivswdev01.ir.intel.com [10.237.217.45]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id w71C7MoY018093; Wed, 1 Aug 2018 13:07:22 +0100 Received: from sivswdev01.ir.intel.com (localhost [127.0.0.1]) by sivswdev01.ir.intel.com with ESMTP id w71C7Mfs003816; Wed, 1 Aug 2018 13:07:22 +0100 Received: (from aburakov@localhost) by sivswdev01.ir.intel.com with LOCAL id w71C7GBn003749; Wed, 1 Aug 2018 13:07:16 +0100 From: Anatoly Burakov To: dev@dpdk.org Cc: Neil Horman , John McNamara , Marko Kovacevic , thomas@monjalon.net, keith.wiles@intel.com Date: Wed, 1 Aug 2018 13:07:16 +0100 Message-Id: <12c37dfc8dda4acbd7b49b00a577c3a9f5cbfbba.1533125146.git.anatoly.burakov@intel.com> X-Mailer: git-send-email 1.7.0.7 Subject: [dpdk-dev] [PATCH] doc: add deprecation notice on external memory support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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] http://patches.dpdk.org/project/dpdk/list/?series=453&state=* [2] https://mails.dpdk.org/archives/dev/2018-July/108002.html Signed-off-by: Anatoly Burakov Acked-by: Keith Wiles Acked-by: Wang, Zhihong Acked-by: Jerin Jacob Acked-by: Yongseok Koh Acked-by: Maxime Coquelin Acked-by: Shreyansh Jain --- 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