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 AD7BD5A68 for ; Mon, 5 Jan 2015 11:38:07 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 05 Jan 2015 02:33:28 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,698,1413270000"; d="scan'208";a="664501153" Received: from bricha3-mobl3.ger.corp.intel.com ([10.243.20.27]) by orsmga002.jf.intel.com with SMTP; 05 Jan 2015 02:38:03 -0800 Received: by (sSMTP sendmail emulation); Mon, 05 Jan 2015 10:38:02 +0025 Date: Mon, 5 Jan 2015 10:38:02 +0000 From: Bruce Richardson To: "Ouyang, Changchun" Message-ID: <20150105103802.GB13152@bricha3-MOBL3> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) 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: Mon, 05 Jan 2015 10:38:08 -0000 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 query the table, if it wants. It should not, however, be able to modify the table, as it is owned by the PF. Regards, /Bruce