From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 6FBBD1B776 for ; Wed, 25 Oct 2017 12:01:28 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D26D7221D4; Wed, 25 Oct 2017 06:01:27 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 25 Oct 2017 06:01:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=2yaMU+IDKA6cX7zke8n1Te3tSZ iXgBJUXXhcf4zljhE=; b=m7R03n18v0SrZJGm9mclFttuRQi52xfDQAjUNC3blS JuRT+bWLrnWbx9Km8loo7jSWAYSMyoHUqxfPsoNM4CbqnbzDLfCWiTbx11VVXz/4 5t5VzR8lMZnBxWkpyX5I/zW0Y1o4noC/IMNLiKuc89pdYScb83A9JNhHywuFG/2o c= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=2yaMU+ IDKA6cX7zke8n1Te3tSZiXgBJUXXhcf4zljhE=; b=gy4h21zcgdNEOMc9vT0t4d sPGbtJT9jW9zs/p08lsGStaZyyPZH5l5x4h3tyyt/1K+ijXxG0b9PIB8VFq7TzQo f8qobsOP47CMhua/y0Feq/Aq97Yldd+iyYk5kJASN7BlrMVHQO3VhJmG+k7Esj6o NreD/gNvrBQzxwGBcGmOw9fyuio9J6Sm+uUKD6YqlivzhzYJwUQb004io/0LKSl6 0meUpoDJkfxRlu6tBxF6rJoDUf3LT1Gv3FEzVqKmzngYM1FimrMnQjY54Qc7MmMc eHO5zwTeXP5gXKXRwZtq5HOlTTsNd0+J1q/ojMdAWAj+UVoKBAFknIjk/5p/VqAQ == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 7E5487FA7E; Wed, 25 Oct 2017 06:01:27 -0400 (EDT) From: Thomas Monjalon To: "Richardson, Bruce" Cc: santosh , dev@dpdk.org, "olivier.matz@6wind.com" , "jerin.jacob@caviumnetworks.com" , "hemant.agrawal@nxp.com" , "Burakov, Anatoly" Date: Wed, 25 Oct 2017 12:01:26 +0200 Message-ID: <1726043.3urDsTveGQ@xps> In-Reply-To: <59AF69C657FD0841A61C55336867B5B0721ECB08@IRSMSX103.ger.corp.intel.com> References: <20170905103119.20511-1-santosh.shukla@caviumnetworks.com> <1947820.k6ijHbkXh2@xps> <59AF69C657FD0841A61C55336867B5B0721ECB08@IRSMSX103.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 5/6] doc: remove dpdk iova aware notice 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: Wed, 25 Oct 2017 10:01:28 -0000 25/10/2017 11:50, Richardson, Bruce: > > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > > Sent: Wednesday, October 25, 2017 10:46 AM > > To: santosh > > Cc: dev@dpdk.org; olivier.matz@6wind.com; jerin.jacob@caviumnetworks.com; > > hemant.agrawal@nxp.com; Burakov, Anatoly > > Subject: Re: [dpdk-dev] [PATCH v3 5/6] doc: remove dpdk iova aware notice > > > > Hi Santosh, > > > > 24/10/2017 07:06, santosh: > > > Hi Thomas, > > > > > > > > > On Tuesday 24 October 2017 01:59 AM, Thomas Monjalon wrote: > > > > 20/10/2017 14:31, Santosh Shukla: > > > >> Removed dpdk iova aware ABI deprecation notice, and updated ABI > > > >> change details in release_17.11.rst. > > > >> > > > >> Signed-off-by: Santosh Shukla > > > >> Acked-by: John McNamara > > > >> --- > > > >> --- a/doc/guides/rel_notes/deprecation.rst > > > >> +++ b/doc/guides/rel_notes/deprecation.rst > > > >> -* eal: An ABI change is planned for 17.11 to make DPDK aware of > > > >> IOVA address > > > >> - translation scheme. > > > >> - Reference to phys address in EAL data-structure or functions may > > > >> change to > > > >> - IOVA address or more appropriate name. > > > >> - The change will be only for the name. > > > >> - Functional aspects of the API or data-structure will remain same. > > > > Sorry, this series cannot be applied as is because it is breaking > > > > more than EAL API. The API of mbuf and mempool are also changed. > > > > We need to choose one of these three options: > > > > 1/ accept to break all API in 17.11 > > > > 2/ postpone the whole series to 18.02 > > > > > > Theme of series is to make dpdk iova aware so I would prefer option 1) > > or 2). > > > However I have no strong opinion on this topic. > > > Lets get more opinion from others about option 1/2/3. > > > > > > > 3/ rename only EAL API in 17.11 and postpone mbuf/mempool > > > > After discussing with Olivier it appeared there is a fourth solution. > > We should not break any API (EAL, mbuf, mempool). > > > > I would like to merge these changes in RC2, but keeping compatibility with > > old names: > > - When you rename a function or a type, you can define a macro for the old > > name, alias the new name. > > Note: using a macro doesn't prevent the ABI being broken if you rename a public function. You'll need to use function versioning too. True We can use an inline function to avoid ABI breakage.