From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 473BF689B for ; Thu, 25 Dec 2014 03:26:26 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP; 24 Dec 2014 18:22:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,640,1413270000"; d="scan'208";a="628900571" Received: from pgsmsx105.gar.corp.intel.com ([10.221.44.96]) by orsmga001.jf.intel.com with ESMTP; 24 Dec 2014 18:26:23 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by PGSMSX105.gar.corp.intel.com (10.221.44.96) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 25 Dec 2014 10:26:22 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.216]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.240]) with mapi id 14.03.0195.001; Thu, 25 Dec 2014 10:26:22 +0800 From: "Ouyang, Changchun" To: Vlad Zolotarov , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v3 0/6] Enable VF RSS for Niantic Thread-Index: AQHQHzm9+XzyM+/AzkmVdIuTG6pu75yeCfEAgAGI4CA= Date: Thu, 25 Dec 2014 02:26:21 +0000 Message-ID: References: <1419389808-9559-1-git-send-email-changchun.ouyang@intel.com> <1419398584-19520-1-git-send-email-changchun.ouyang@intel.com> <549A9A28.10401@cloudius-systems.com> In-Reply-To: <549A9A28.10401@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] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v3 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: Thu, 25 Dec 2014 02:26:26 -0000 Hi, > -----Original Message----- > From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com] > Sent: Wednesday, December 24, 2014 6:49 PM > To: Ouyang, Changchun; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3 0/6] Enable VF RSS for Niantic >=20 >=20 > On 12/24/14 07:22, Ouyang Changchun wrote: > > This patch enables VF RSS for Niantic, which allow each VF having at mo= st 4 > queues. > > The actual queue number per VF depends on the total number of pool, > > which is determined by the total number of VF at PF initialization > > stage and the number of queue specified in config: > > 1) If the number of VF is in the range from 1 to 32 and the number of > > rxq is 4('--rxq 4' in testpmd), then there is totally 32 > > pools(ETH_32_POOLS), and each VF have 4 queues; > > > > 2)If the number of VF is in the range from 33 to 64 and the number of > > rxq is 2('--rxq 2' in testpmd), then there is totally 64 > > pools(ETH_64_POOLS), and each VF have 2 queues; > > > > On host, to enable VF RSS functionality, rx mq mode should be set as > > ETH_MQ_RX_VMDQ_RSS or ETH_MQ_RX_RSS mode, and SRIOV mode > should be activated(max_vfs >=3D 1). > > It also needs config VF RSS information like hash function, RSS key, RS= S key > length. > > > > The limitation for Niantic VF RSS is: > > the hash and key are shared among PF and all VF, the RETA table with > > 128 entries are also shared among PF and all VF. So it is not good > > idea to query the hash and reta content per VF on guest, instead, it ma= kes > sense to query them on host(PF). > > > > v3 change: > > - More cleanup; >=20 > This series is still missing the appropriate patches in the > rte_eth_dev_info_get() flow to return a reta_size for a VF device; and to > rte_eth_dev_rss_reta_query() in the context of a VF device (I haven't > noticed the initialization of a > dev->dev_ops->reta_query for the VF device in this series). >=20 > Without these code bits it's impossible to work with the VF devices in th= e RSS > context the same way we work with the PF devices. It means that we'll hav= e > to do some special branching to handle the VF device and this voids the > whole meaning of the framework which in turn is very unfortunate. >=20 Again pls try to query reta content on pf/host, this is due to hw limitatio= n, It don't affect any functionality, just the querying is special. Before this patch, customer often was notified Niantic can't support vf rss= , But with lots of experiments and find that it still has limited vf rss func= tionality. Even on that, linux ixgbe driver has at most 2 queues per vf, But the dpdk could enable 4 queues per vf. In summary, dpdk could support vf rss on Niantic with at most 4 queues per = vf, but the querying of reta is very limited due to the HW limitation. =20 Hope you are on the same page now. Thanks Changchun