From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id AA4BE569A for ; Tue, 6 Jan 2015 02:04:47 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 05 Jan 2015 17:04:46 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,702,1413270000"; d="scan'208";a="657263112" Received: from kmsmsx151.gar.corp.intel.com ([172.21.73.86]) by fmsmga002.fm.intel.com with ESMTP; 05 Jan 2015 17:04:45 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 6 Jan 2015 09:04:15 +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; Tue, 6 Jan 2015 09:04:14 +0800 From: "Ouyang, Changchun" To: "Richardson, Bruce" Thread-Topic: [dpdk-dev] [PATCH v3 0/6] Enable VF RSS for Niantic Thread-Index: AQHQHzm9+XzyM+/AzkmVdIuTG6pu75yd/AcAgAGLwpCAEVsDAIABd4KQ Date: Tue, 6 Jan 2015 01:04:13 +0000 Message-ID: References: <1419389808-9559-1-git-send-email-changchun.ouyang@intel.com> <1419398584-19520-1-git-send-email-changchun.ouyang@intel.com> <549A8E7C.7010806@cloudius-systems.com> <20150105103802.GB13152@bricha3-MOBL3> In-Reply-To: <20150105103802.GB13152@bricha3-MOBL3> 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 Cc: "dev@dpdk.org" 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: Tue, 06 Jan 2015 01:04:48 -0000 > -----Original Message----- > From: Richardson, Bruce > Sent: Monday, January 5, 2015 6:38 PM > To: Ouyang, Changchun > Cc: Vlad Zolotarov; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3 0/6] Enable VF RSS for Niantic >=20 > On Thu, Dec 25, 2014 at 01:46:54AM +0000, Ouyang, Changchun wrote: > > Hi, > > > > > -----Original Message----- > > > From: Vlad Zolotarov [mailto:vladz@cloudius-systems.com] > > > Sent: Wednesday, December 24, 2014 5:59 PM > > > To: Ouyang, Changchun; dev@dpdk.org > > > Subject: Re: [dpdk-dev] [PATCH v3 0/6] Enable VF RSS for Niantic > > > > > > > > On the contrary - it's a very good idea! We use DPDK on Amazon's > > > guests with enhanced networking and we have no access to the PF. We > > > still need to know the RSS redirection rules for our VF pool. From > > > the 82599 spec, chapter > > > 4.6.10.1.1: "redirection table is common to all the pools and only > > > indicates the queue inside the pool to use once the pool is chosen". > > > In that case we need to get the whole 128 entries of the RETA. Is > > > there a reason why we can't have it? > > > > > Due to hardware limitation, VF could not query its own reta table, > > because there is not its own reta, The reta table shared by pf and all = vfs. > > If you need know it, query them on pf is feasible way to do it. > > > It's not feasible if you only have access to a guest. :-) IMHO since the = guest is > seeing the results of the RSS redirection table, it should be able to que= ry the > table, if it wants. It should not, however, be able to modify the table, = as it is > owned by the PF. Understand the situation, but the real issue is that the guest has no way t= o know the rss redirection table, so it could not query it. =20