From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Michael Chan <michael.chan@broadcom.com>,
Sathya Perla <sathya.perla@broadcom.com>,
simon.horman@netronome.com, davem@davemloft.net
Subject: Re: [RFC] switchdev: clarify ndo_get_phys_port_name() formats
Date: Wed, 26 Jul 2017 07:48:40 +0200 [thread overview]
Message-ID: <20170726054840.GA1845@nanopsycho> (raw)
In-Reply-To: <20170725051344.2040-1-jakub.kicinski@netronome.com>
Tue, Jul 25, 2017 at 07:13:44AM CEST, jakub.kicinski@netronome.com wrote:
>We are still in position where we can suggest uniform naming
>convention for ndo_get_phys_port_name(). switchdev.txt file
>already contained a suggestion of how to name external ports.
>Since the use of switchdev for SR-IOV NIC's eswitches is growing,
>establish a format for ports of those devices as well.
>
>Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
>---
> Documentation/networking/switchdev.txt | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
>diff --git a/Documentation/networking/switchdev.txt b/Documentation/networking/switchdev.txt
>index 3e7b946dea27..7c4b6025fb4b 100644
>--- a/Documentation/networking/switchdev.txt
>+++ b/Documentation/networking/switchdev.txt
>@@ -119,9 +119,17 @@ into 4 10G ports, resulting in 4 port netdevs, the device can give a unique
> SUBSYSTEM=="net", ACTION=="add", ATTR{phys_switch_id}=="<phys_switch_id>", \
> ATTR{phys_port_name}!="", NAME="swX$attr{phys_port_name}"
>
>-Suggested naming convention is "swXpYsZ", where X is the switch name or ID, Y
>-is the port name or ID, and Z is the sub-port name or ID. For example, sw1p1s0
>-would be sub-port 0 on port 1 on switch 1.
>+Suggested formats of the port name returned by ndo_get_phys_port_name are:
>+ - pA for external ports;
>+ - pAsB for split external ports;
>+ - pfC for PF ports (so called PF representors);
>+ - pfCvfD for VF ports (so called VF representors).
I think it would make sense if the driver would just fill-up a struct in
the ndo call and core would generate the string.
>+Where A is the port name or ID; B is the sub-port name or ID; C is PCIe
>+Physical Function name or ID and D is PCIe Virtual Function name or ID.
>+
>+Suggested naming convention for switches is "swX", where X is the switch name
>+or ID, plus the port name. For example, sw1p1s0 would be sub-port 0 on port 1
>+on switch 1.
>
> Port Features
> ^^^^^^^^^^^^^
>--
>2.11.0
>
next prev parent reply other threads:[~2017-07-26 5:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 16:34 [PATCH net-next 00/10] bnxt_en: Updates for net-next Michael Chan
2017-07-24 16:34 ` [PATCH net-next 01/10] bnxt_en: Update firmware interface spec to 1.8.0 Michael Chan
2017-07-24 16:34 ` [PATCH net-next 02/10] bnxt_en: Retrieve the hardware bridge mode from the firmware Michael Chan
2017-07-24 16:34 ` [PATCH net-next 03/10] bnxt_en: Implement ndo_bridge_{get|set}link methods Michael Chan
2017-07-24 16:34 ` [PATCH net-next 04/10] bnxt_en: Add bnxt_get_num_stats() to centrally get the number of ethtool stats Michael Chan
2017-07-24 16:34 ` [PATCH net-next 05/10] bnxt_en: Allow the user to set ethtool stats-block-usecs to 0 Michael Chan
2017-07-24 16:34 ` [PATCH net-next 06/10] bnxt_en: Report firmware DCBX agent Michael Chan
2017-07-24 16:34 ` [PATCH net-next 07/10] bnxt_en: Set ETS min_bw parameter for older firmware Michael Chan
2017-07-24 16:34 ` [PATCH net-next 08/10] bnxt_en: add support to enable VF-representors Michael Chan
2017-07-25 2:28 ` kbuild test robot
2017-07-24 16:34 ` [PATCH net-next 09/10] bnxt_en: add vf-rep RX/TX and netdev implementation Michael Chan
2017-07-24 16:34 ` [PATCH net-next 10/10] bnxt_en: add support for port_attr_get and and get_phys_port_name Michael Chan
2017-07-25 2:44 ` kbuild test robot
2017-07-25 4:06 ` Jakub Kicinski
2017-07-25 4:21 ` David Miller
2017-07-25 4:45 ` Jakub Kicinski
2017-07-25 5:13 ` [RFC] switchdev: clarify ndo_get_phys_port_name() formats Jakub Kicinski
2017-07-25 15:22 ` Andy Gospodarek
2017-07-25 22:26 ` Jakub Kicinski
2017-07-26 1:48 ` Andy Gospodarek
2017-07-26 2:34 ` Jakub Kicinski
2017-07-26 17:54 ` Andy Gospodarek
2017-07-26 5:48 ` Jiri Pirko [this message]
2017-07-26 8:13 ` Jakub Kicinski
2017-07-26 9:23 ` Or Gerlitz
2017-07-26 20:11 ` Jakub Kicinski
2017-07-27 10:30 ` Or Gerlitz
2017-07-28 2:31 ` [RFC] switchdev: generate phys_port_name in the core Jakub Kicinski
2017-07-28 2:37 ` Jakub Kicinski
2017-07-28 5:35 ` Jiri Pirko
2017-07-28 5:58 ` Jiri Pirko
2017-07-28 7:28 ` Jakub Kicinski
2017-07-28 7:27 ` Jakub Kicinski
2017-07-28 14:13 ` Andrew Lunn
2017-07-25 9:55 ` [PATCH net-next 10/10] bnxt_en: add support for port_attr_get and and get_phys_port_name Sathya Perla
2017-07-25 22:27 ` Jakub Kicinski
2017-07-26 9:13 ` Or Gerlitz
2017-07-25 0:32 ` [PATCH net-next 00/10] bnxt_en: Updates for net-next 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=20170726054840.GA1845@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sathya.perla@broadcom.com \
--cc=simon.horman@netronome.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).