From: Stephen Hemminger <stephen@networkplumber.org>
To: <skori@marvell.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>, <dev@dpdk.org>,
Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [PATCH v7 1/1] ethdev: add support to provide link type
Date: Wed, 20 Aug 2025 11:58:18 -0700 [thread overview]
Message-ID: <20250820115818.0a3628ee@hermes.local> (raw)
In-Reply-To: <20250820175317.3063659-1-skori@marvell.com>
On Wed, 20 Aug 2025 23:22:31 +0530
<skori@marvell.com> wrote:
Patch does not apply cleanly to next-net, there is fuzz.
> diff --git a/lib/ethdev/ethdev_trace.h b/lib/ethdev/ethdev_trace.h
> index 482befc209..bc6c3a4a02 100644
> --- a/lib/ethdev/ethdev_trace.h
> +++ b/lib/ethdev/ethdev_trace.h
> @@ -2110,6 +2110,13 @@ RTE_TRACE_POINT_FP(
> rte_trace_point_emit_string(ret);
> )
>
> +RTE_TRACE_POINT_FP(
> + rte_eth_trace_link_connector_to_str,
> + RTE_TRACE_POINT_ARGS(uint8_t link_connector, const char *ret),
> + rte_trace_point_emit_u8(link_connector);
> + rte_trace_point_emit_string(ret);
> +);
> +
IMHO adding a trace point to a helper function like this is just
extra clutter, remove it.
> +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))) &&
> + link_connector_str[link_connector])
> + str = link_connector_str[link_connector];
This can be simplified to:
if (link_connector < RTE_DIM(link_connector_str))
str = link_connector_str[link_connector];
Since enum's act like int in C, no need for all that casting.
> +/**
> + * @warning
> + * @b EXPERIMENTAL: this API may change without prior notice.
> + *
> + * This function converts an Ethernet link type to a string.
> + *
> + * @param link_connector
> + * The link type to convert.
> + * @return
> + * The string representation of the link type.
> + */
> +__rte_experimental
> +const char *rte_eth_link_connector_to_str(enum rte_eth_link_connector link_connector);
Need to document that it returns NULL for invalid link_connector values.
prev parent reply other threads:[~2025-08-20 18:58 UTC|newest]
Thread overview: 35+ 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
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 [this message]
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=20250820115818.0a3628ee@hermes.local \
--to=stephen@networkplumber.org \
--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).