From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Sunil Kumar Kori" <skori@marvell.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>
Cc: <dev@dpdk.org>, "Thomas Monjalon" <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH v11 1/1] ethdev: add link connector type
Date: Thu, 11 Sep 2025 11:41:42 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FEE0@smartserver.smartshare.dk> (raw)
In-Reply-To: <20250911084943.2383151-1-skori@marvell.com>
> From: Sunil Kumar Kori <skori@marvell.com>
>
> Adding link connector parameter to provide the type
> of connection for a port like twisted pair, fiber etc.
>
> Also added an API to convert the RTE_ETH_LINK_CONNECTOR_XXX
> to a readable string.
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> ---
[...]
> +* **Added ethdev API to get link connector.**
> +
> + * Added API to report type of link connection for a port.
> + The following connectors are enumerated:
> +
> + * NONE
> + * TP
> + * FIBER
> + * BNC
> + * DAC
> + * XFI, SFI
> + * MII, SGMII, QSGMII
> + * AUI, XLAUI, GAUI, AUI, CAUI, LAUI
> + * SFP, SFP_PLUS, SFP28, SFP_DD
> + * QSFP, QSFP_PLUS, QSFP28, QSFP56, QSFP_DD
> + * OTHER
Please use the string names, not the enum name, here.
E.g. Twisted Pair instead of TP, and SFP+ instead of SFP_PLUS.
> +
> + By default, it reports ``RTE_ETH_LINK_CONNECTOR_NONE``
> + unless driver specifies it.
> +
> * **Added speed 800G.**
>
> Added Ethernet link speed for 800 Gb/s as it is well standardized in
> IEEE,
> @@ -124,6 +144,9 @@ ABI Changes
> * eal: The structure ``rte_mp_msg`` alignment has been updated to 8
> bytes to limit unaligned
> accesses in messages payload.
>
> +* ethdev: Added ``link_connector`` field to ``rte_eth_link`` structure
> + to report type of link connection for a port.
connection -> connector
[...]
> /**
> * A structure used to retrieve link-level information of an Ethernet
> port.
> */
> @@ -343,6 +382,7 @@ struct rte_eth_link {
> uint16_t link_duplex : 1; /**<
> RTE_ETH_LINK_[HALF/FULL]_DUPLEX */
> uint16_t link_autoneg : 1; /**<
> RTE_ETH_LINK_[AUTONEG/FIXED] */
> uint16_t link_status : 1; /**<
> RTE_ETH_LINK_[DOWN/UP] */
> + uint16_t link_connector : 5; /**<
> RTE_ETH_LINK_CONNECTOR_XXX */
Please use 6 bits instead of 5, so it is more future proof.
With the connector types already defined, 5 bits only leaves room for six more connector types.
Remember to update the value of RTE_ETH_LINK_CONNECTOR_OTHER from 31 to 63.
-Morten
next prev parent reply other threads:[~2025-09-11 9:41 UTC|newest]
Thread overview: 55+ 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
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 [this message]
2025-09-11 10:37 ` Sunil Kumar Kori
2025-09-11 10:34 ` [PATCH v12 " skori
2025-09-11 10:39 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35E9FEE0@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=thomas@monjalon.net \
/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).