> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Polehn, Mike A
> Sent: Thursday, November 05, 2015 5:59 PM
> To: Richardson, Bruce; Shaham Fridenberg
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] SR-IOV: API to tell VF from PF
>
: Thursday, November 5, 2015 7:51 AM
To: Polehn, Mike A; Shaham Fridenberg
Cc: dev at dpdk.org
Subject: RE: [dpdk-dev] SR-IOV: API to tell VF from PF
> -Original Message-
> From: Polehn, Mike A
> Sent: Thursday, November 5, 2015 3:43 PM
> To: Richardson, Bruce ; Shaham Fridenb
> -Original Message-
> From: Polehn, Mike A
> Sent: Thursday, November 5, 2015 3:43 PM
> To: Richardson, Bruce ; Shaham Fridenberg
>
> Cc: dev at dpdk.org
> Subject: RE: [dpdk-dev] SR-IOV: API to tell VF from PF
>
> I can think of a very good reason to want
to do high value processing.
Mike
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
Sent: Thursday, November 5, 2015 1:51 AM
To: Shaham Fridenberg
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] SR-IOV: API to tell VF from PF
On Thu, Nov 05, 2015 at 09
On Thu, Nov 05, 2015 at 09:39:19AM +, 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
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
6 matches
Mail list logo