[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5775BD44.7080906@gmail.com>
Date: Thu, 30 Jun 2016 17:45:56 -0700
From: John Fastabend <john.fastabend@...il.com>
To: Saeed Mahameed <saeedm@...lanox.com>,
"David S. Miller" <davem@...emloft.net>
Cc: netdev@...r.kernel.org, Or Gerlitz <ogerlitz@...lanox.com>,
Hadar Hen-Zion <hadarh@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>,
Andy Gospodarek <gospo@...ulusnetworks.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
John Fastabend <john.r.fastabend@...el.com>
Subject: Re: [PATCH net-next V2 08/16] net/devlink: Add E-Switch mode control
On 16-06-30 08:23 AM, Saeed Mahameed wrote:
> From: Or Gerlitz <ogerlitz@...lanox.com>
>
> Add the commands to set and show the mode of SRIOV E-Switch, two modes
> are supported:
>
> * legacy: operating in the "old" L2 based mode (DMAC --> VF vport)
>
> * switchdev: the E-Switch is referred to as whitebox switch configured
> using standard tools such as tc, bridge, openvswitch etc. To allow
> working with the tools, for each VF, a VF representor netdevice is
> created by the E-Switch manager vendor device driver instance (e.g PF).
>
> Signed-off-by: Or Gerlitz <ogerlitz@...lanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@...lanox.com>
> ---
OK I can't come up with a better name and Jiri/Or convinced me this
should work ok so this works for me.
One question though going forward. We have devices with multiple
"switches" in them how does this work in a devlink environment? Do
we need some way to enumerate the switches and identify them. In
which case this attribute would be a global setting.
Thanks,
John
Powered by blists - more mailing lists