All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Parav Pandit <parav@mellanox.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@mellanox.com,
	moshe@mellanox.com, vladyslavt@mellanox.com, saeedm@mellanox.com,
	leon@kernel.org
Subject: Re: [PATCH net-next 1/2] devlink: Introduce devlink port flavour virtual
Date: Tue, 3 Mar 2020 14:44:35 -0800	[thread overview]
Message-ID: <20200303144435.5aedb892@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200303141243.7608-2-parav@mellanox.com>

On Tue,  3 Mar 2020 08:12:42 -0600 Parav Pandit wrote:
> Currently mlx5 PCI PF and VF devlink devices register their ports as
> physical port in non-representors mode.
> 
> Introduce a new port flavour as virtual so that virtual devices can
> register 'virtual' flavour to make it more clear to users.
> 
> An example of one PCI PF and 2 PCI virtual functions, each having
> one devlink port.
> 
> $ devlink port show
> pci/0000:06:00.0/1: type eth netdev ens2f0 flavour physical port 0
> pci/0000:06:00.2/1: type eth netdev ens2f2 flavour virtual port 0
> pci/0000:06:00.3/1: type eth netdev ens2f3 flavour virtual port 0
> 
> Reviewed-by: Jiri Pirko <jiri@mellanox.com>
> Signed-off-by: Parav Pandit <parav@mellanox.com>

Acked-by: Jakub Kicinski <kuba@kernel.org>

  reply	other threads:[~2020-03-03 22:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 14:12 [PATCH net-next 0/2] devlink: Introduce devlink port flavour virtual Parav Pandit
2020-03-03 14:12 ` [PATCH net-next 1/2] " Parav Pandit
2020-03-03 22:44   ` Jakub Kicinski [this message]
2020-03-03 14:12 ` [PATCH net-next 2/2] net/mlx5e: Use devlink virtual flavour for VF devlink port Parav Pandit
2020-03-03 23:40 ` [PATCH net-next 0/2] devlink: Introduce devlink port flavour virtual David Miller

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=20200303144435.5aedb892@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jiri@mellanox.com \
    --cc=leon@kernel.org \
    --cc=moshe@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=vladyslavt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.