From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 89DA71D9E for ; Wed, 23 May 2018 00:17:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 041EA21AF0; Tue, 22 May 2018 18:17:16 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 22 May 2018 18:17:16 -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=jXSjiutUpcVXH9WZGFxVcGTBjg 2RYkFqkTctx9quFd4=; b=sR4x/6k4NpzN9Pr1dDEnwGBtTqIm6AmOLf96dELzFz U2pZxFEMVz62wLMshAFzx7vK+jsPSnvXDZ/jyKJ1MVNdAfpKy61+samCAswB2M+I fb/2/Fr3DojWcpgbdlH0z7ulxviJHL2eljGF6cozSnydPtdlF4f5OH3snLvRDIOM 0= 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=jXSjiu tUpcVXH9WZGFxVcGTBjg2RYkFqkTctx9quFd4=; b=l3dRZoKkDjiv/Mz4pV/sL5 96Wu3gUFrNfWe+D3gDfsMAkiWZ2wKllY71yt3jA3vNU6iNZJCIMaDbQhCO4eC2WR gYf7dEDQlwYGvsDJQsYQ9I1TJmzQgTedIbqeIr4hhfhsjPmWhObjOLfwz5FtVsgM AfdjCoJpLkjoqsfDJfN9FKOEIvtYVCECeLWSitb6yiBoq6Pa8F7s0xrhEFZ0Q9eu +yL8x4mgUpo779al0eZVT0Fn84jxkhkMFozzWLkYzy13FwlMhhD6PJTUH0RVmi6H a2zM5XAKOcUEzxFK1hQiemFSAntSvmhElruaT4BxIP4Cr4uWCT1WyIhJN7Xgj7OQ == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: 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 4D8C8E4434; Tue, 22 May 2018 18:17:14 -0400 (EDT) From: Thomas Monjalon To: Nikhil Agarwal Cc: dev@dpdk.org, david.hunt@intel.com, nikhil.agarwal@nxp.com, hemant.agrawal@nxp.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, shahafs@mellanox.com Date: Wed, 23 May 2018 00:17:13 +0200 Message-ID: <1867579.zxL6BAlCOx@xps> In-Reply-To: <20171212100520.20502-1-nikhil.agarwal@linaro.org> References: <20171212100520.20502-1-nikhil.agarwal@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info 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, 22 May 2018 22:17:16 -0000 12/12/2017 11:05, Nikhil Agarwal: > Currently, if the rte_eth_rx_burst() function returns a value less than > *nb_pkts*, the application will assume that no more packets are present. > > Some of the hw queue based hardware can only support smaller burst for RX > and TX and thus break the expectation of the rx_burst API. > > This patch adds support to provide the maximum burst size that can be > supported by a given PMD. The dev_info is being memset to '0' in > rte_ethdev library. The value of '0' indicates that any value for burst > size can be supported i.e. no change for existing PMDs. > > The application can now use the lowest available max_burst_size value > for rte_eth_rx_burst. > > Signed-off-by: Nikhil Agarwal > --- > @@ -1047,6 +1047,7 @@ struct rte_eth_dev_info { > /** Configured number of rx/tx queues */ > uint16_t nb_rx_queues; /**< Number of RX queues. */ > uint16_t nb_tx_queues; /**< Number of TX queues. */ > + uint16_t max_burst_size; /**< MAX burst size, 0 for no limit. */ > }; What is the status of this proposal? Recently, the preferred tuning have been added by "ethdev: support PMD-tuned Tx/Rx parameters" http://dpdk.org/commit/3be82f5cc5