[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO2PR11MB0088BB6334851B5B51E5851497240@CO2PR11MB0088.namprd11.prod.outlook.com>
Date: Thu, 30 Jun 2016 19:04:16 +0000
From: Yuval Mintz <Yuval.Mintz@...gic.com>
To: Hariprasad Shenai <hariprasad@...lsio.com>,
David Miller <davem@...emloft.net>,
"stephen@...workplumber.org" <stephen@...workplumber.org>
CC: netdev <netdev@...r.kernel.org>,
"nirranjan@...lsio.com" <nirranjan@...lsio.com>,
"leedom@...lsio.com" <leedom@...lsio.com>,
"kumaras@...lsio.com" <kumaras@...lsio.com>
Subject: Re: [PATCHv2 net-next 1/3] net: Add provision to specify pf number
while assigning VF mac
> Chelsio T4/T5 cards have SR-IOV Capabilities on Physical Functions
> 0..3 and the administrative Driver(cxgb4) attaches to Physical Function 4.
> Each of the Physical Functions 0..3 can support up to 16 Virtual
> Functions. With the current Linux APIs, a 2-Port card would only be
> able to use the Virtual Functions on Physical Functions 0..1 and not
> allow the Virtual Functions on Physical Functions 2..3 to be used since
> there are no Ports 2..3 on a 2-Port card.
>
> Also the current ip commands takes netdev as one of the argument, and
> it assumes a 1-to-1 mapping of Network Ports, Physical Functions and the
> SR-IOV Virtual Functions of those Physical Functions. But it is not
> true in our case and won't work for us.
>
> Added a new argument to specify the PF number associated with the VF, to
> fix this.
I don't get it - what's the exact definition of 'Physical Function'?
Are we talking PCI functions? Logical partitons? Something else?
Powered by blists - more mailing lists