From: John Fastabend <john.fastabend@gmail.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
Hadar Hen-Zion <hadarh@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
John Fastabend <john.r.fastabend@intel.com>
Subject: Re: [PATCH net-next V2 08/16] net/devlink: Add E-Switch mode control
Date: Thu, 30 Jun 2016 17:45:56 -0700 [thread overview]
Message-ID: <5775BD44.7080906@gmail.com> (raw)
In-Reply-To: <1467300215-14199-9-git-send-email-saeedm@mellanox.com>
On 16-06-30 08:23 AM, Saeed Mahameed wrote:
> From: Or Gerlitz <ogerlitz@mellanox.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@mellanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@mellanox.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
next prev parent reply other threads:[~2016-07-01 0:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:23 [PATCH net-next V2 00/16] Mellanox 100G SRIOV E-Switch offload and VF representors Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 01/16] net/mlx5: E-Switch, Add operational mode to the SRIOV e-Switch Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 02/16] net/mlx5: E-Switch, Add support for the sriov offloads mode Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 03/16] net/mlx5: E-Switch, Add miss rule for " Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 04/16] net/mlx5: E-Switch, Add API to create send-to-vport rules Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 05/16] net/mlx5: Introduce offloads steering namespace Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 06/16] net/mlx5: E-Switch, Add offloads table Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 07/16] net/mlx5: E-Switch, Add API to create vport rx rules Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 08/16] net/devlink: Add E-Switch mode control Saeed Mahameed
2016-06-30 15:40 ` Jiri Pirko
2016-07-01 0:45 ` John Fastabend [this message]
2016-07-01 4:00 ` Or Gerlitz
2016-06-30 15:23 ` [PATCH net-next V2 09/16] net/mlx5: Add devlink interface Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 10/16] net/mlx5e: Add devlink based SRIOV mode changes Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 11/16] net/mlx5e: Create NIC global resources only once Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 12/16] net/mlx5e: TIRs management refactoring Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 13/16] net/mlx5e: Mark enabled RQTs instances explicitly Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 14/16] net/mlx5e: Add support for multiple profiles Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 15/16] net/mlx5: Add Representors registration API Saeed Mahameed
2016-06-30 15:23 ` [PATCH net-next V2 16/16] net/mlx5e: Introduce SRIOV VF representors Saeed Mahameed
2016-07-01 10:16 ` [PATCH net-next V2 00/16] Mellanox 100G SRIOV E-Switch offload and " David Miller
2016-07-01 11:04 ` Saeed Mahameed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5775BD44.7080906@gmail.com \
--to=john.fastabend@gmail.com \
--cc=davem@davemloft.net \
--cc=gospo@cumulusnetworks.com \
--cc=hadarh@mellanox.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@mellanox.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).