From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: SR-IOV: API to tell VF from PF Date: Thu, 5 Nov 2015 09:50:52 +0000 Message-ID: <20151105095052.GA15324@bricha3-MOBL3> References: <2E654B490240B7449C846A96A8D8FE0CC43A4C67@ILMB2.corp.radware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" To: Shaham Fridenberg Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 2143C37A4 for ; Thu, 5 Nov 2015 10:51:18 +0100 (CET) Content-Disposition: inline In-Reply-To: <2E654B490240B7449C846A96A8D8FE0CC43A4C67@ILMB2.corp.radware.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Nov 05, 2015 at 09:39:19AM +0000, Shaham Fridenberg wrote: > Hey all, > > Is there some API to tell VF from PF? > > Only way I found so far is deducing that from driver name in the rte_eth_devices struct. > > Thanks, > Shaham Hi Shaham, yes, checking the driver name is probably the only way to do so. However, why do you need or want to know this? If you want to know the capabilities of a device basing it on a list of known device types is probably not the best way. Regards, /Bruce