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 046B15F18 for ; Tue, 20 Mar 2018 12:05:09 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6B0BA215F3; Tue, 20 Mar 2018 07:05:09 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 20 Mar 2018 07:05:09 -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=nP9XUIvRQY3yZ4UUAKn05HT593 NAcv/iRbdZ1Mzw4xQ=; b=Zif+Wzxd3jU/842IBpEDkqPp2z2mLs2koV1g1oAwB6 HeatmFX5JpsPe02FNlNkp+cJsbK33HNyvL7DPwkJk88Bb0x22mNuzYs5npk4NQmd BIOy3BoDAY1z2pxXmiALwnU7cEILcTvPvLCiKluEhL07Y7eZMTArtSVrxeypoBVk k= 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=fm2; bh=nP9XUI vRQY3yZ4UUAKn05HT593NAcv/iRbdZ1Mzw4xQ=; b=iWsMVVgZICyxqOh1kU1t+F Kt0QutRbyEJPzw6wpgvlSwmgfuSc3VDaOpm7VYr/6v5FTD+EGyi41cBAJObTFjk0 HOjxt6ydSUOItfulINWRjFS2ZyR/RLr87mYabW5GfrI3Nf2STCPyf4hszasm1Cd0 bFHh+8MgNoqLOdisAfvi8kkdVirj/4YM4V6yUWy14cEXpBwIlsZizdcOMiF1ukvT GfiHHIz3/OCTYPr4U3jExkyaDlCjgoQh3syNbq6eWT/wgDHLJ+BusupEgLsK/atI zFh0Bqd0iu3BNto8wZ/3EsSwMkOXl2lmnRCu3HHrXf3LpJhW06vINcdbqXRsQ4TA == 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 648CE7E1D4; Tue, 20 Mar 2018 07:05:08 -0400 (EDT) From: Thomas Monjalon To: Andrew Rybchenko Cc: Olivier Matz , dev@dpdk.org, Santosh Shukla , Jerin Jacob , Hemant Agrawal , Shreyansh Jain Date: Tue, 20 Mar 2018 12:04:54 +0100 Message-ID: <2352592.k8uHYFHRCe@xps> In-Reply-To: <5f02489c-9bd8-3265-4b55-9feb88d22cb5@solarflare.com> References: <1516713372-10572-1-git-send-email-arybchenko@solarflare.com> <20180319170322.webhsihrpdcfns4y@platinum> <5f02489c-9bd8-3265-4b55-9feb88d22cb5@solarflare.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 0/9] mempool: prepare to add bucket driver 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: Tue, 20 Mar 2018 11:05:10 -0000 20/03/2018 11:09, Andrew Rybchenko: > On 03/19/2018 08:03 PM, Olivier Matz wrote: > >> I've kept rte_mempool_populate_iova_tab() intact since it seems to > >> be not directly related XMEM API functions. > > The function rte_mempool_populate_iova_tab() (actually, it was > > rte_mempool_populate_phys_tab()) was introduced to support XMEM > > API. In my opinion, it can also be deprecated. > > CC Thomas > > Definitely OK for me. It is not listed in deprecation notice included in > 18.02, > but I think it is OK to deprecate it in 18.05 (since we're not removing, > but just deprecating it). Yes it is OK to deprecate this function in addition to other mempool ones already listed as planned to be deprecated.