From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A0877A04D8; Mon, 21 Sep 2020 16:19:13 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 863C91DA91; Mon, 21 Sep 2020 16:19:13 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 4E2F01D70E for ; Mon, 21 Sep 2020 16:19:11 +0200 (CEST) IronPort-SDR: 1YWlft+bSDUN8bfne/iGjZ/LUCYNVFFNdIMPiU3Yb13E4TiBqSSkA3CZ6u5ogNlQAmEDrIqiDK TwpJdKdtsdaw== X-IronPort-AV: E=McAfee;i="6000,8403,9750"; a="224533793" X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="224533793" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 07:19:06 -0700 IronPort-SDR: KNSC/kDQJxsSdIpWymKfFjJm8acQQMiDl/BaelsTzc3OyPZpJZmwgb5uKiHjBZqZduzbAOKnWH AX+5Rxkpofyg== X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="309050819" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.217.64]) ([10.213.217.64]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 07:19:04 -0700 To: Chengchang Tang , dev@dpdk.org Cc: linuxarm@huawei.com, thomas@monjalon.net, arybchenko@solarflare.com, wenzhuo.lu@intel.com, maryam.tahhan@intel.com References: <1592483709-7076-1-git-send-email-tangchengchang@huawei.com> <1600694558-19120-1-git-send-email-tangchengchang@huawei.com> From: Ferruh Yigit Message-ID: Date: Mon, 21 Sep 2020 15:19:03 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.2.2 MIME-Version: 1.0 In-Reply-To: <1600694558-19120-1-git-send-email-tangchengchang@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v5 0/2] add Rx buffer size for rxq info structure 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 9/21/2020 2:22 PM, Chengchang Tang wrote: > In common practice, PMD configure the Rx buffer size which indicate the > buffer length could be used for HW in receiving packets according to the > data room size of the object in mempool. But in fact, the final value is > related to the specifications of HW, and its values will affect the number > of fragments in receiving packets when scatter is enabled. By the way, > some PMDs may force to enable scatter when the MTU is bigger than the HW > Rx buffer size. > > At present, we have no way to expose relevant information to upper layer > users. So, add a field named rx_buf_size in rte_eth_rxq_info to indicate > the buffer size used in receiving packets for HW. And this field is > optional, so there is no need to forcibly update all PMDs. > > This patchset also update testpmd, proc-info tools and add hns3 PMD > implementation. > > v5: > - squash oneline app patches and deprecation remove with ethdev patch > > Chengchang Tang (2): > ethdev: add a field for rxq info structure > net/hns3: add Rx buffer size to Rx qinfo query > Series applied to dpdk-next-net/main, thanks.