From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: [PATCH v5 2/2] ethdev: get the supported pool for a port Date: Mon, 2 Oct 2017 16:31:50 +0200 Message-ID: <20171002143149.fjlr7n5cft3lyrc5@platinum> References: <20170911151837.25092-1-santosh.shukla@caviumnetworks.com> <20171001091440.10232-1-santosh.shukla@caviumnetworks.com> <20171001091440.10232-3-santosh.shukla@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, thomas@monjalon.net, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com To: Santosh Shukla Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 1EC971B22C for ; Mon, 2 Oct 2017 16:31:58 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20171001091440.10232-3-santosh.shukla@caviumnetworks.com> 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 Sun, Oct 01, 2017 at 02:44:40PM +0530, Santosh Shukla wrote: > Now that dpdk supports more than one mempool drivers and > each mempool driver works best for specific PMD, example: > - sw ring based mempool for Intel PMD drivers. > - dpaa2 HW mempool manager for dpaa2 PMD driver. > - fpa HW mempool manager for Octeontx PMD driver. > > Application would like to know the best mempool handle > for any port. > > Introducing rte_eth_dev_pool_ops_supported() API, > which allows PMD driver to advertise > his supported pool capability to the application. > > Supported pools are categorized in below priority:- > - Best mempool handle for this port (Highest priority '0') > - Port supports this mempool handle (Priority '1') > > Signed-off-by: Santosh Shukla Acked-by: Olivier Matz