From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 416AFA04DD; Tue, 10 Nov 2020 17:10:20 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1A2245928; Tue, 10 Nov 2020 17:10:19 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 021025913 for ; Tue, 10 Nov 2020 17:10:16 +0100 (CET) IronPort-SDR: L1aP9fr6ssiSN5XBv7ZVJ8kEk8EeqvS0MdBwa/tFKsk/b4AzZJOEWQWoDiZScyAHc6oQkS0v8O oKYwQbZ120kQ== X-IronPort-AV: E=McAfee;i="6000,8403,9801"; a="234165070" X-IronPort-AV: E=Sophos;i="5.77,466,1596524400"; d="scan'208";a="234165070" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Nov 2020 08:10:09 -0800 IronPort-SDR: iCtvFtW7lVlR7iTNb2M8mVwy+B7ZYw8o+XFsm7R4gy+G51mkLJ/6aIW8PGy8npN6XqAtZ3ffBy RhPRv/g2pnYQ== X-IronPort-AV: E=Sophos;i="5.77,466,1596524400"; d="scan'208";a="473480073" Received: from bricha3-mobl.ger.corp.intel.com ([10.213.241.186]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 10 Nov 2020 08:10:08 -0800 Date: Tue, 10 Nov 2020 16:10:05 +0000 From: Bruce Richardson To: Stephen Hemminger Cc: dev@dpdk.org Message-ID: <20201110161005.GM1641@bricha3-MOBL.ger.corp.intel.com> References: <20200922143202.8755-1-stephen@networkplumber.org> <20201105223602.5965-1-stephen@networkplumber.org> <20201105223602.5965-7-stephen@networkplumber.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201105223602.5965-7-stephen@networkplumber.org> Subject: Re: [dpdk-dev] [PATCH v9 6/6] doc: update release notes now for block allow changes 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" On Thu, Nov 05, 2020 at 02:36:02PM -0800, Stephen Hemminger wrote: > Remove the deprecation notice and add description to the release notes. > > Signed-off-by: Stephen Hemminger > --- > doc/guides/rel_notes/deprecation.rst | 23 ----------------------- > doc/guides/rel_notes/release_20_11.rst | 11 +++++++++++ > 2 files changed, 11 insertions(+), 23 deletions(-) > > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst > index f3258eb3f725..d459a25eabe3 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -28,29 +28,6 @@ Deprecation Notices > * kvargs: The function ``rte_kvargs_process`` will get a new parameter > for returning key match count. It will ease handling of no-match case. > > -* eal: The terms blacklist and whitelist to describe devices used > - by DPDK will be replaced in the 20.11 relase. > - This will apply to command line arguments as well as macros. > - > - The macro ``RTE_DEV_BLACKLISTED`` will be replaced with ``RTE_DEV_EXCLUDED`` > - and ``RTE_DEV_WHITELISTED`` will be replaced with ``RTE_DEV_INCLUDED`` > - ``RTE_BUS_SCAN_BLACKLIST`` and ``RTE_BUS_SCAN_WHITELIST`` will be > - replaced with ``RTE_BUS_SCAN_EXCLUDED`` and ``RTE_BUS_SCAN_INCLUDED`` > - respectively. Likewise ``RTE_DEVTYPE_BLACKLISTED_PCI`` and > - ``RTE_DEVTYPE_WHITELISTED_PCI`` will be replaced with > - ``RTE_DEVTYPE_EXCLUDED`` and ``RTE_DEVTYPE_INCLUDED``. > - > - The old macros will be marked as deprecated in 20.11 and any > - usage will cause a compile warning. They will be removed in > - a future release. > - > - The command line arguments to ``rte_eal_init`` will change from > - ``-b, --pci-blacklist`` to ``-x, --exclude`` and > - ``-w, --pci-whitelist`` to ``-i, --include``. > - The old command line arguments will continue to be accepted in 20.11 > - but will cause a runtime warning message. The old arguments will > - be removed in a future release. > - > * eal: The function ``rte_eal_remote_launch`` will return new error codes > after read or write error on the pipe, instead of calling ``rte_panic``. > > diff --git a/doc/guides/rel_notes/release_20_11.rst b/doc/guides/rel_notes/release_20_11.rst > index 6bbd6ee93922..df955e2214c4 100644 > --- a/doc/guides/rel_notes/release_20_11.rst > +++ b/doc/guides/rel_notes/release_20_11.rst > @@ -644,6 +644,17 @@ API Changes > * sched: Removed ``tb_rate``, ``tc_rate``, ``tc_period`` and ``tb_size`` > from ``struct rte_sched_subport_params``. > > +* eal: The selection of devices on the EAL command line has been > + changed from ``--pci-blacklist`` and ``--pci-whitelist`` > + to ``--block`` and ``--allow``. The short form option for > + using a device is now ``-a`` instead of ``-w``. > + > + The internal macros for ``RTE_DEV_BLACKLISTED`` and ``RTE_DEV_WHITELISTED`` > + have been replaced with ``RTE_DEV_BLOCKED`` and ``RTE_DEV_ALLOWED``. > + > + There are compatibility macros and command line mappings to accept > + the old values but applications and scripts are strongly encouraged > + to migrate to the new names. > Are all the other macro changes non-user visible? Do they need to be called out somewhere, or is the above enough? /Bruce