[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180831201321.GA4590@localhost.localdomain>
Date: Fri, 31 Aug 2018 17:13:22 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Or Gerlitz <gerlitz.or@...il.com>,
Simon Horman <simon.horman@...ronome.com>,
Andy Gospodarek <andy@...yhouse.net>,
"mchan@...adcom.com" <mchan@...adcom.com>,
Jiri Pirko <jiri@...nulli.us>,
Alexander Duyck <alexander.duyck@...il.com>,
Frederick Botha <frederick.botha@...ronome.com>,
nick viljoen <nick.viljoen@...ronome.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: phys_port_id in switchdev mode?
On Tue, Aug 28, 2018 at 08:43:51PM +0200, Jakub Kicinski wrote:
> Ugh, CC: netdev..
>
> On Tue, 28 Aug 2018 20:05:39 +0200, Jakub Kicinski wrote:
> > Hi!
> >
> > I wonder if we can use phys_port_id in switchdev to group together
> > interfaces of a single PCI PF? Here is the problem:
On Mellanox cards, this is already possible via phys_switch_id, as
each PF has its own phys_switch_id. So all VFs with a given
phys_switch_id belong to the PF with that same phys_switch_id.
I understand this is a vendor-specific design, but if you have the
same phys_switch_id across PFs, does it really matter on which PF the
VF was created on?
Marcelo
Powered by blists - more mailing lists