From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 5D4143256; Mon, 12 Nov 2018 17:55:25 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DC74122209; Mon, 12 Nov 2018 11:55:24 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 12 Nov 2018 11:55:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=F2ajfdTjeRQHPydSjRJhPTyDzkP1E0PEsrv29DgdWLY=; b=NTtpnv2ELpDO 8LlQ+Iwl8LN3xuYBY+U6UIOOxzoy5MydkEtwvgoWvVZimG7YzxRCQ7Bjhkc1RUkC ffpuoex0LaYRfhNJHxlttPPhrPOyFPlfliHpZzXyAWaQ/5Y8t2GjWlSv7+TYE3De 1whRo2JmJImYa3IWRfVWAjKHe+akLKo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=F2ajfdTjeRQHPydSjRJhPTyDzkP1E0PEsrv29DgdW LY=; b=thYyZ0NL1LCO5hZzozLmVbyjjnTxhY5drztVYnxfEo2gbOzW+y4RHDPLV X+EYzALNZR4d2f4gQZKfbPPguAIA3A1bqW6TgCL2KZ14GoO7bbEYCH/f15vvdsfy 1vOD3dBd2Ai5CcQpUZ1XFzgSupZs+h5x4kJBGDrj7Z8FC7mK1qNIhAsrNF58IWLS D4PXxzd1iHQHRu4JDvGH2XVgtdCUs6RTghNgELKR3gU5xpR5MY0ezdjl4e/5ejuP ZwG/Mpwhg7hWHH5pq1TGT0sSzQhi7qjTFfgw1Q81xwsSThNMhOVrErZPqCaq4dU0 MaIVN8MU+3Wbib8VPbkX0KNRoHVxA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 6335AE4679; Mon, 12 Nov 2018 11:55:23 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: techboard@dpdk.org, "Ananyev, Konstantin" , "Richardson, Bruce" , "Burakov, Anatoly" , Jerin Jacob , "dev@dpdk.org" Date: Mon, 12 Nov 2018 17:55:22 +0100 Message-ID: <2240482.x5FLNkSg3a@xps> In-Reply-To: <20181112084353.506b2786@xeon-e3> References: <20181110091727.GA20155@jerin> <2601191342CEEE43887BDE71AB977258010CE49651@IRSMSX106.ger.corp.intel.com> <20181112084353.506b2786@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-techboard] DPDK techboard minutes of October 24 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: , X-List-Received-Date: Mon, 12 Nov 2018 16:55:25 -0000 12/11/2018 17:43, Stephen Hemminger: > On Mon, 12 Nov 2018 12:36:45 +0000 > "Ananyev, Konstantin" wrote: > > From: Richardson, Bruce > > > From: techboard [mailto:techboard-bounces@dpdk.org] On Behalf Of Ananyev, > > > > Konstantin > > > > > > > > Hi Anatoly, > > > > > > > > > > Meeting notes for the DPDK technical board meeting held on > > > > > > 2018-10-24 [...] > > > > > > 0) DPDK acceptance policy on un-implemented API > > > > > > - New APIs without implementation is not accepted. > > > > > > - In order to accept a new API, At minimum > > > > > > a) Need to provide an unit test case or example application > > > > > > b) If the API is about HW abstraction, at least one driver should be > > > > > > implemented. Preferably two. > > > > > > c) If there are strong objections on ML about the need for more than > > > > > > one driver for a specific API then the technical board can make a > > > > > > decision. > > > > > > - Konstantin volunteered to send existing un-implemented API to the > > > > > > mailing list. > > > > > > - The existing un-implemented APIs will be deprecated in v19.05. > > > > > > - Deprecated un-implemented API will be removed in v19.08 > > > > > > > > > > > > > > > > Does this also apply to unimplemented parts of the existing API? For > > > > > example, malloc API has long had a "name" parameter which goes > > > > > unimplemented through entire lifetime of DPDK project. It would be > > > > > good to drop this thing entirely as it's clear it's not going to be > > > > > implemented any time soon :) > > > > > > > > > > > > > Sounds like a good idea to me. > > > > Konstantin > > > > > > While a good idea in theory, I'm not sure the cost-benefit pays off for this one. Given the fact that the extra parameter is rather harmless, > > > the benefit seems minimal compared to the effort which would be involved for everyone to have to change every rte_malloc call in every > > > app! > > > > I am agree about massive amount of changes, though I thought Anatoly sort of volunteering for it :) > > About benefit - it would save us spilling/restoring one register for each rte_malloc() call. > > Probably not that important, as rte_malloc() usually is used from data-path, but still. > > Plus it doesn't look good to have a function with parameter that would never be used. > > Konstantin > > > > > > I agree, we should do these kind of cleanups, but only on ABI breaking releases. > Too late now for 18.11 and next one is probably 19.11 We can discuss which release can break ABI. I think 19.05 is a good candidate.