netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
	<sgoutham@marvell.com>, <sbhatta@marvell.com>,
	<hkelam@marvell.com>
Subject: Re: [net-next PATCH v7 00/10] Introduce RVU representors
Date: Mon, 1 Jul 2024 20:12:15 -0700	[thread overview]
Message-ID: <20240701201215.5b68e164@kernel.org> (raw)
In-Reply-To: <20240628133517.8591-1-gakula@marvell.com>

On Fri, 28 Jun 2024 19:05:07 +0530 Geetha sowjanya wrote:
> This series adds representor support for each rvu devices.
> When switchdev mode is enabled, representor netdev is registered
> for each rvu device. In implementation of representor model, 
> one NIX HW LF with multiple SQ and RQ is reserved, where each
> RQ and SQ of the LF are mapped to a representor. A loopback channel
> is reserved to support packet path between representors and VFs.
> CN10K silicon supports 2 types of MACs, RPM and SDP. This
> patch set adds representor support for both RPM and SDP MAC
> interfaces.
> 
> - Patch 1: Refactors and exports the shared service functions.
> - Patch 2: Implements basic representor driver.
> - Patch 3: Add devlink support to create representor netdevs that
>   can be used to manage VFs.
> - Patch 4: Implements basec netdev_ndo_ops.
> - Patch 5: Installs tcam rules to route packets between representor and
> 	   VFs.
> - Patch 6: Enables fetching VF stats via representor interface
> - Patch 7: Adds support to sync link state between representors and VFs .
> - Patch 8: Enables configuring VF MTU via representor netdevs.
> - Patch 9: Add representors for sdp MAC.
> - Patch 10: Add devlink port support.
> 
> Command to create VF representor
> #devlink dev eswitch set pci/0002:1c:00.0 mode switchdev
> VF representors are created for each VF when switch mode is set switchdev on representor PCI device
> # devlink dev eswitch set pci/0002:1c:00.0  mode switchdev 
> # ip link show
> 25: r0p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
>     link/ether 32:0f:0f:f0:60:f1 brd ff:ff:ff:ff:ff:ff
> 26: r1p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
>     link/ether 3e:5d:9a:4d:e7:7b brd ff:ff:ff:ff:ff:ff
> 
> #devlink dev
> pci/0002:01:00.0
> pci/0002:02:00.0
> pci/0002:03:00.0
> pci/0002:04:00.0
> pci/0002:05:00.0
> pci/0002:06:00.0
> pci/0002:07:00.0
> 
> ~# devlink port
> pci/0002:1c:00.0/0: type eth netdev r0p1v0 flavour pcipf controller 0 pfnum 1 vfnum 0 external false splittable false
> pci/0002:1c:00.0/1: type eth netdev r1p1v1 flavour pcivf controller 0 pfnum 1 vfnum 1 external false splittable false
> pci/0002:1c:00.0/2: type eth netdev r2p1v2 flavour pcivf controller 0 pfnum 1 vfnum 2 external false splittable false
> pci/0002:1c:00.0/3: type eth netdev r3p1v3 flavour pcivf controller 0 pfnum 1 vfnum 3 external false splittable false

Please document the state before and after switching modes, and record
this information in 
Documentation/networking/device_drivers/ethernet/marvell/octeontx2.rst

In the commands above you seem to operate on a pci/0002:1c:00.0 devlink
instance, and yet devlink dev does not list it. You have 2 netdevs,
8 devlinks, 4 ports, and no PF instance. It does not add up..

  parent reply	other threads:[~2024-07-02  3:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 13:35 [net-next PATCH v7 00/10] Introduce RVU representors Geetha sowjanya
2024-06-28 13:35 ` [net-next PATCH v7 01/10] octeontx2-pf: Refactoring RVU driver Geetha sowjanya
2024-07-01 10:49   ` Simon Horman
2024-06-28 13:35 ` [net-next PATCH v7 02/10] octeontx2-pf: RVU representor driver Geetha sowjanya
2024-07-01 10:49   ` Simon Horman
2024-07-03 17:33   ` William Tu
2024-07-04  9:33     ` [EXTERNAL] " Geethasowjanya Akula
2024-06-28 13:35 ` [net-next PATCH v7 03/10] octeontx2-pf: Create representor netdev Geetha sowjanya
2024-07-01 10:50   ` Simon Horman
2024-06-28 13:35 ` [net-next PATCH v7 04/10] octeontx2-pf: Add basic net_device_ops Geetha sowjanya
2024-07-01 10:50   ` Simon Horman
2024-06-28 13:35 ` [net-next PATCH v7 05/10] octeontx2-af: Add packet path between representor and VF Geetha sowjanya
2024-07-01 10:50   ` Simon Horman
2024-06-28 13:35 ` [net-next PATCH v7 06/10] octeontx2-pf: Get VF stats via representor Geetha sowjanya
2024-07-02  3:13   ` Jakub Kicinski
2024-07-02  6:41     ` [EXTERNAL] " Geethasowjanya Akula
2024-07-02 13:56       ` Jakub Kicinski
2024-07-03  9:08         ` Geethasowjanya Akula
2024-07-03 18:33           ` Jakub Kicinski
2024-07-04  9:39             ` Geethasowjanya Akula
2024-06-28 13:35 ` [net-next PATCH v7 07/10] octeontx2-pf: Add support to sync link state between representor and VFs Geetha sowjanya
2024-06-28 13:35 ` [net-next PATCH v7 08/10] octeontx2-pf: Configure VF mtu via representor Geetha sowjanya
2024-06-28 13:35 ` [net-next PATCH v7 09/10] octeontx2-pf: Add representors for sdp MAC Geetha sowjanya
2024-07-01 10:51   ` Simon Horman
2024-06-28 13:35 ` [net-next PATCH v7 10/10] octeontx2-pf: Add devlink port support Geetha sowjanya
2024-07-02  3:12 ` Jakub Kicinski [this message]
2024-07-03  9:10   ` [EXTERNAL] Re: [net-next PATCH v7 00/10] Introduce RVU representors Geethasowjanya Akula
2024-07-03 10:44 ` Michal Swiatkowski
2024-07-03 14:34   ` [EXTERNAL] " Geethasowjanya Akula
2024-07-04  7:14     ` Michal Swiatkowski
2024-07-04 13:48       ` Geethasowjanya Akula
2024-07-05  8:34         ` Michal Swiatkowski
2024-07-05 11:12           ` Geethasowjanya Akula

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=20240701201215.5b68e164@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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).