From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wes1-so2.wedos.net (wes1-so2.wedos.net [46.28.106.16]) by dpdk.org (Postfix) with ESMTP id 2E5512BE4 for ; Thu, 7 Apr 2016 19:12:03 +0200 (CEST) Received: from pcviktorin.fit.vutbr.cz (pcviktorin.fit.vutbr.cz [147.229.13.147]) by wes1-so2.wedos.net (Postfix) with ESMTPSA id 3qgpzk5xRyz2sM; Thu, 7 Apr 2016 19:12:02 +0200 (CEST) Date: Thu, 7 Apr 2016 19:09:50 +0200 From: "Jan Viktorin" To: David Marchand Cc: "dev@dpdk.org" , Olivier Matz , Thomas Monjalon Message-ID: <20160407190950.52f58009@pcviktorin.fit.vutbr.cz> In-Reply-To: References: <1460043197-13707-1-git-send-email-david.marchand@6wind.com> <20160407174616.416ec249@pcviktorin.fit.vutbr.cz> Organization: RehiveTech MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes for device objects X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 17:12:03 -0000 On Thu, 7 Apr 2016 19:00:43 +0200 David Marchand wrote: > On Thu, Apr 7, 2016 at 5:46 PM, Jan Viktorin wrote: > > On Thu, 7 Apr 2016 17:33:17 +0200 > > David Marchand wrote: > > > >> Following discussions with Jan, here is a deprecation notice to prepare for > >> hotplug and rte_device changes to come in 16.07. > >> > >> Signed-off-by: David Marchand > >> --- > >> doc/guides/rel_notes/deprecation.rst | 12 ++++++++++++ > >> 1 file changed, 12 insertions(+) > >> > >> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst > >> index 98d5529..d749e5d 100644 > >> --- a/doc/guides/rel_notes/deprecation.rst > >> +++ b/doc/guides/rel_notes/deprecation.rst > >> @@ -8,6 +8,18 @@ API and ABI deprecation notices are to be posted here. > >> Deprecation Notices > >> ------------------- > >> > >> +* The ethdev hotplug API is going to be moved to EAL with a notification > >> + mechanism added to crypto and ethdev libraries so that hotplug is now > >> + available to both of them. This API will be stripped of the device arguments > >> + so that it only cares about hotplugging. > >> + > >> +* Structures embodying pci and vdev devices are going to be reworked to > >> + integrate new common rte_device / rte_driver objects (see > >> + http://dpdk.org/ml/archives/dev/2016-January/031390.html). > >> + ethdev and crypto libraries will then only handle those objects so that they > >> + do not need to care about the kind of devices that are being used, making it > >> + easier to add new buses later. > > > > As a result, the current rte_driver structure will be renamed to > > rte_module and probably reworked in some way due to its semantics and > > potential name clash with the new rte_driver struct. > > If we just introduce some macros like RTE_MODULE_INIT() / > RTE_MODULE_EXIT(), we don't need a rte_module object at the moment ? > Well, possibly, we don't need it. At least, it might be hidden and not being a part of the API/ABI. Do you need an ack for this?