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>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3 1/1] ethdev: add support to provide link type
Date: Wed, 13 Aug 2025 12:25:51 +0200 [thread overview]
Message-ID: <1975832.6tgchFWduM@thomas> (raw)
In-Reply-To: <20250813084508.1446318-1-skori@marvell.com>
13/08/2025 10:43, skori@marvell.com:
> + * Ethernet port type
You mean "link port type"
> + */
> +#define RTE_ETH_LINK_TYPE_NONE 0 /**< Not defined */
> +#define RTE_ETH_LINK_TYPE_TP 1 /**< Twisted Pair */
> +#define RTE_ETH_LINK_TYPE_AUI 2 /**< Attachment Unit Interface */
> +#define RTE_ETH_LINK_TYPE_MII 3 /**< Media Independent Interface */
> +#define RTE_ETH_LINK_TYPE_FIBRE 4 /**< Fibre */
In general we use the US word "fiber",
but we are not very consistent, so it is not a strong opinion.
> +#define RTE_ETH_LINK_TYPE_BNC 5 /**< BNC */
> +#define RTE_ETH_LINK_TYPE_DA 6 /**< Direct Attach copper */
> +#define RTE_ETH_LINK_TYPE_SGMII 7 /**< SGMII */
> +#define RTE_ETH_LINK_TYPE_QSGMII 8 /**< QSGMII */
> +#define RTE_ETH_LINK_TYPE_XFI 9 /**< XFI */
> +#define RTE_ETH_LINK_TYPE_SFI 10 /**< SFI */
> +#define RTE_ETH_LINK_TYPE_XLAUI 11 /**< XLAUI */
> +#define RTE_ETH_LINK_TYPE_GAUI 12 /**< GAUI */
> +#define RTE_ETH_LINK_TYPE_XAUI 13 /**< XAUI */
> +#define RTE_ETH_LINK_TYPE_GBASE 14 /**< GBASE */
> +#define RTE_ETH_LINK_TYPE_CAUI 15 /**< CAUI */
> +#define RTE_ETH_LINK_TYPE_LAUI 16 /**< LAUI */
> +#define RTE_ETH_LINK_TYPE_SFP 17 /**< SFP */
> +#define RTE_ETH_LINK_TYPE_SFP_DD 18 /**< SFP_DD */
You should use more full words in comments, at least for DD.
> +#define RTE_ETH_LINK_TYPE_SFP_PLUS 19 /**< SFP_PLUS */
Please add more spaces to allow a correct alignment.
> +#define RTE_ETH_LINK_TYPE_SFP28 20 /**< SFP28 */
> +#define RTE_ETH_LINK_TYPE_QSFP 21 /**< QSFP */
> +#define RTE_ETH_LINK_TYPE_QSFP_PLUS 22 /**< QSFP_PLUS */
> +#define RTE_ETH_LINK_TYPE_QSFP28 23 /**< QSFP28 */
> +#define RTE_ETH_LINK_TYPE_QSFP56 24 /**< QSFP56 */
> +#define RTE_ETH_LINK_TYPE_QSFP_DD 25 /**< QSFP_DD */
> +#define RTE_ETH_LINK_TYPE_OTHER 0x1F /**< Other type */
Why the last one is in hexadecimal? and why 1F?
Is there a logic in the order and numbering for this list?
Why not using an enum?
Thanks
next prev parent reply other threads:[~2025-08-13 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 11:31 [PATCH] " 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 [this message]
2025-08-13 12:16 ` Ivan Malov
2025-08-13 14:17 ` Stephen Hemminger
2025-08-13 15:04 ` 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=1975832.6tgchFWduM@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--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 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).