From: Thomas Monjalon <thomas@monjalon.net>
To: Sunil Kumar Kori <skori@marvell.com>
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Stephen Hemminger <stephen@networkplumber.org>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH v10 1/1] ethdev: add support to provide link type
Date: Mon, 08 Sep 2025 11:23:07 +0200 [thread overview]
Message-ID: <5037037.31r3eYUQgx@thomas> (raw)
In-Reply-To: <20250908085256.1866407-1-skori@marvell.com>
Hello,
The title can be simply "ethdev: add link type".
08/09/2025 10:51, skori@marvell.com:
> +* **Added ethdev API in library.*
Please be more specific, we don't need to group all ethdev changes together.
Each new API feature deserves a separate bullet.
> +
> + * Added API to report type of link connection for a port.
> + By default, it reports ``RTE_ETH_LINK_CONNECTOR_NONE``
> + unless driver specifies it.
I think you need to explain what is a type (copper, fiber, etc).
[...]
> +RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_eth_link_connector_to_str, 25.11)
> +const char *
> +rte_eth_link_connector_to_str(enum rte_eth_link_connector link_connector)
> +{
> + static const char * const link_connector_str[] = {
> + [RTE_ETH_LINK_CONNECTOR_NONE] = "None",
> + [RTE_ETH_LINK_CONNECTOR_TP] = "Twisted Pair",
> + [RTE_ETH_LINK_CONNECTOR_AUI] = "Attachment Unit Interface",
> + [RTE_ETH_LINK_CONNECTOR_MII] = "Media Independent Interface",
> + [RTE_ETH_LINK_CONNECTOR_FIBER] = "Fiber",
> + [RTE_ETH_LINK_CONNECTOR_BNC] = "BNC",
> + [RTE_ETH_LINK_CONNECTOR_DAC] = "Direct Attach Copper",
> + [RTE_ETH_LINK_CONNECTOR_SGMII] = "SGMII",
> + [RTE_ETH_LINK_CONNECTOR_QSGMII] = "QSGMII",
> + [RTE_ETH_LINK_CONNECTOR_XFI] = "XFI",
> + [RTE_ETH_LINK_CONNECTOR_SFI] = "SFI",
> + [RTE_ETH_LINK_CONNECTOR_XLAUI] = "XLAUI",
> + [RTE_ETH_LINK_CONNECTOR_GAUI] = "GAUI",
> + [RTE_ETH_LINK_CONNECTOR_XAUI] = "XAUI",
> + [RTE_ETH_LINK_CONNECTOR_CAUI] = "CAUI",
> + [RTE_ETH_LINK_CONNECTOR_LAUI] = "LAUI",
> + [RTE_ETH_LINK_CONNECTOR_SFP] = "SFP",
> + [RTE_ETH_LINK_CONNECTOR_SFP_DD] = "SFP-DD",
> + [RTE_ETH_LINK_CONNECTOR_SFP_PLUS] = "SFP+",
> + [RTE_ETH_LINK_CONNECTOR_SFP28] = "SFP28",
> + [RTE_ETH_LINK_CONNECTOR_QSFP] = "QSFP",
> + [RTE_ETH_LINK_CONNECTOR_QSFP_PLUS] = "QSFP+",
> + [RTE_ETH_LINK_CONNECTOR_QSFP28] = "QSFP28",
> + [RTE_ETH_LINK_CONNECTOR_QSFP56] = "QSFP56",
> + [RTE_ETH_LINK_CONNECTOR_QSFP_DD] = "QSFP-DD",
> + [RTE_ETH_LINK_CONNECTOR_OTHER] = "Other",
> + };
> + const char *str = NULL;
> +
> + if (link_connector < ((enum rte_eth_link_connector)RTE_DIM(link_connector_str)))
> + str = link_connector_str[link_connector];
> +
> + return str;
> +}
So we say link connector, not link type as in the title and descriptions?
[...]
> +enum rte_eth_link_connector {
> + RTE_ETH_LINK_CONNECTOR_NONE = 0, /**< Not defined */
> + RTE_ETH_LINK_CONNECTOR_TP, /**< Twisted Pair */
> + RTE_ETH_LINK_CONNECTOR_AUI, /**< Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_MII, /**< Media Independent Interface */
> + RTE_ETH_LINK_CONNECTOR_FIBER, /**< Optical Fiber Link */
> + RTE_ETH_LINK_CONNECTOR_BNC, /**< BNC Link type for RF connection */
> + RTE_ETH_LINK_CONNECTOR_DAC, /**< Direct Attach copper */
> + RTE_ETH_LINK_CONNECTOR_SGMII, /**< Serial Gigabit Media Independent Interface */
> + RTE_ETH_LINK_CONNECTOR_QSGMII, /**< Link to multiplex 4 SGMII over one serial link */
> + RTE_ETH_LINK_CONNECTOR_XFI, /**< 10 Gigabit Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_SFI, /**< 10 Gigabit Serial Interface for optical network */
> + RTE_ETH_LINK_CONNECTOR_XLAUI, /**< 40 Gigabit Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_GAUI, /**< Gigabit Interface for 50/100/200 Gbps */
> + RTE_ETH_LINK_CONNECTOR_XAUI, /**< 10 Gigabit Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_CAUI, /**< 100 Gigabit Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_LAUI, /**< 50 Gigabit Attachment Unit Interface */
> + RTE_ETH_LINK_CONNECTOR_SFP, /**< Pluggable module for 1 Gigabit */
> + RTE_ETH_LINK_CONNECTOR_SFP_PLUS, /**< Pluggable module for 10 Gigabit */
> + RTE_ETH_LINK_CONNECTOR_SFP28, /**< Pluggable module for 25 Gigabit */
> + RTE_ETH_LINK_CONNECTOR_SFP_DD, /**< Pluggable module for 100 Gigabit */
> + RTE_ETH_LINK_CONNECTOR_QSFP, /**< Module to mutiplex 4 SFP i.e. 4*1=4 Gbps */
> + RTE_ETH_LINK_CONNECTOR_QSFP_PLUS, /**< Module to mutiplex 4 SFP_PLUS i.e. 4*10=40 Gbps */
> + RTE_ETH_LINK_CONNECTOR_QSFP28, /**< Module to mutiplex 4 SFP28 i.e. 4*25=100 Gbps */
> + RTE_ETH_LINK_CONNECTOR_QSFP56, /**< Module to mutiplex 4 SFP56 i.e. 4*50=200 Gbps */
> + RTE_ETH_LINK_CONNECTOR_QSFP_DD, /**< Module to mutiplex 4 SFP_DD i.e. 4*100=400 Gbps */
> + RTE_ETH_LINK_CONNECTOR_OTHER = 31, /**< non-physical interfaces like virtio, ring etc.
> + * It also includes unknown connector types,
> + * i.e. physical connectors not yet defined in this
> + * list of connector types.
It is confusing whether we use NONE or OTHER for unknown types.
next prev parent reply other threads:[~2025-09-08 9:23 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:31 [PATCH] ethdev: add support to provide link type skori
2025-06-05 15:26 ` Stephen Hemminger
2025-06-06 9:28 ` [PATCH v2 1/1] " skori
2025-06-06 9:54 ` Morten Brørup
2025-06-06 15:23 ` Stephen Hemminger
2025-06-10 5:02 ` [EXTERNAL] " Sunil Kumar Kori
2025-06-10 6:45 ` Morten Brørup
2025-08-13 7:42 ` Sunil Kumar Kori
2025-08-13 8:42 ` [PATCH] " skori
2025-08-13 8:43 ` [PATCH v3 1/1] " skori
2025-08-13 10:25 ` Thomas Monjalon
2025-08-13 12:16 ` Ivan Malov
2025-08-13 14:17 ` Stephen Hemminger
2025-08-14 5:09 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-13 15:04 ` Stephen Hemminger
2025-08-14 8:10 ` [PATCH v4 " skori
2025-08-14 9:04 ` Morten Brørup
2025-08-14 16:15 ` Stephen Hemminger
2025-08-18 6:21 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-18 7:24 ` Morten Brørup
2025-08-18 8:13 ` Ivan Malov
2025-08-18 8:39 ` Morten Brørup
2025-08-18 8:50 ` Ivan Malov
2025-08-18 22:41 ` Jochen Behrens
2025-08-19 9:57 ` Morten Brørup
2025-08-18 6:20 ` Sunil Kumar Kori
2025-08-14 16:07 ` Stephen Hemminger
2025-08-18 6:13 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-19 5:51 ` [PATCH v5 " skori
2025-08-19 16:29 ` Stephen Hemminger
2025-08-20 9:55 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-20 11:13 ` [PATCH v6 " skori
2025-08-20 12:51 ` Morten Brørup
2025-08-20 17:52 ` [PATCH v7 " skori
2025-08-20 18:58 ` Stephen Hemminger
2025-08-21 4:51 ` [EXTERNAL] " Sunil Kumar Kori
2025-08-21 15:20 ` Stephen Hemminger
2025-08-22 4:34 ` Sunil Kumar Kori
2025-08-21 5:32 ` [PATCH v8 " skori
2025-08-29 20:33 ` Stephen Hemminger
2025-09-01 5:05 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-01 5:44 ` [PATCH v9 " skori
2025-09-06 17:51 ` Stephen Hemminger
2025-09-08 6:21 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-08 8:54 ` Sunil Kumar Kori
2025-09-08 8:51 ` [PATCH v10 " skori
2025-09-08 9:23 ` Thomas Monjalon [this message]
2025-09-11 8:12 ` [EXTERNAL] " Sunil Kumar Kori
2025-09-10 0:50 ` Stephen Hemminger
2025-09-10 17:21 ` Thomas Monjalon
2025-09-11 8:48 ` [PATCH v11 1/1] ethdev: add link connector type skori
2025-09-11 9:41 ` Morten Brørup
2025-09-11 10:37 ` Sunil Kumar Kori
2025-09-11 10:34 ` [PATCH v12 " skori
2025-09-11 10:39 ` Morten Brørup
2025-09-15 16:32 ` Stephen Hemminger
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=5037037.31r3eYUQgx@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=stephen@networkplumber.org \
/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.