From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 2B76C2A1A for ; Fri, 19 Dec 2014 02:35:40 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 18 Dec 2014 17:35:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,604,1413270000"; d="scan'208,217";a="650224251" Received: from kmsmsx151.gar.corp.intel.com ([172.21.73.86]) by fmsmga002.fm.intel.com with ESMTP; 18 Dec 2014 17:35:22 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 19 Dec 2014 09:35:21 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.216]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.5]) with mapi id 14.03.0195.001; Fri, 19 Dec 2014 09:35:20 +0800 From: "Ouyang, Changchun" To: Vlad Zolotarov , "dev@dpdk.org" Thread-Topic: [PATCH 0/6] Enable VF RSS for Niantic Thread-Index: AQHQGqshdrEfxtxvrU6a8lyaEz9UkJyUy08AgAFUSDA= Date: Fri, 19 Dec 2014 01:35:20 +0000 Message-ID: References: <1418897516-25918-1-git-send-email-vladz@cloudius-systems.com> <5492D13C.4020006@cloudius-systems.com> In-Reply-To: <5492D13C.4020006@cloudius-systems.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH 0/6] Enable VF RSS for Niantic X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2014 01:35:41 -0000 My response as below. From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com] Sent: Thursday, December 18, 2014 9:06 PM To: dev@dpdk.org; Ouyang, Changchun Subject: Re: [PATCH 0/6] Enable VF RSS for Niantic On 12/18/14 12:11, Vlad Zolotarov wrote: From: Changchun Ouyang This patch enables VF RSS for Niantic, which allow each VF having at most 4= queues. The actual queue number per VF depends on the number of VF: VF number from 1~32: 4 queues per VF; VF number from 33~max vf num: 2 queues per VF; On host, to enable VF RSS functionality, mq mode should be set as ETH_MQ_RX= _VMDQ_RSS or ETH_MQ_RX_RSS mode, and SRIOV mode should be activated. It also needs config VF RSS information like hash function, RSS key, RSS ke= y length. This patch series is missing a few things: 1. Taking into the consideration the number of Rx queues requested by a = user in the rte_eth_dev_configure(). Changchun: yes, will have a v2 to consider it, as I say in my previous resp= onse. 1. dev->dev_ops->reta_query used by a rte_eth_dev_rss_reta_query() is st= ill not initialized for a VF. Thus there is no way to query the RSS table Changchun: do you mean query rss table on guest? Niantic doesn't have separ= ate reta for a specific vf, the reta is shared by pf and all vf. Do you think of returning all reta contents for each vf make sense? Or any= other insight here? 1. rte_eth_dev_info_get() returns reta_size =3D=3D 0 when called for a V= F function. Changchun: same as above. Your insight here are welcome here. thanks Changchun