From: "Min Hu (Connor)" <humin29@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Declan Doherty <declan.doherty@intel.com>,
Keith Wiles <keith.wiles@intel.com>
Subject: [dpdk-dev] Questions about rte_eth_link_speed_to_str API
Date: Mon, 13 Sep 2021 16:45:43 +0800 [thread overview]
Message-ID: <29b75903-d212-c6e6-eedf-e3bc92ab816a@huawei.com> (raw)
Hi all,
I have questions about rte_eth_link_speed_to_str API.
The API converts link speed to string for display, But it only
supports the following speeds, like that:
case ETH_SPEED_NUM_NONE: return "None";
case ETH_SPEED_NUM_10M: return "10 Mbps";
case ETH_SPEED_NUM_100M: return "100 Mbps";
case ETH_SPEED_NUM_1G: return "1 Gbps";
case ETH_SPEED_NUM_2_5G: return "2.5 Gbps";
case ETH_SPEED_NUM_5G: return "5 Gbps";
case ETH_SPEED_NUM_10G: return "10 Gbps";
case ETH_SPEED_NUM_20G: return "20 Gbps";
case ETH_SPEED_NUM_25G: return "25 Gbps";
case ETH_SPEED_NUM_40G: return "40 Gbps";
case ETH_SPEED_NUM_50G: return "50 Gbps";
case ETH_SPEED_NUM_56G: return "56 Gbps";
case ETH_SPEED_NUM_100G: return "100 Gbps";
case ETH_SPEED_NUM_200G: return "200 Gbps";
case ETH_SPEED_NUM_UNKNOWN: return "Unknown";
default: return "Invalid";
In some cases, like bonding, for example, three slaves which
link speed are 10Gbps, so link speed of bonding port will be
30Gbps, but it shows "Invalid".
Is this reasonable？ any comments will be welcome.
Best wishes
next reply other threads:[~2021-09-13 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 8:45 Min Hu (Connor) [this message]
2021-09-13 10:26 ` Thomas Monjalon
2021-09-14 3:25 ` Min Hu (Connor)
2021-09-14 6:59 ` Stephen Hemminger
2021-09-14 13:04 ` Min Hu (Connor)
2021-09-16 2:56 ` [dpdk-dev] [RFC] ethdev: improve link speed to string Min Hu (Connor)
2021-09-16 6:22 ` Andrew Rybchenko
2021-09-16 8:16 ` Min Hu (Connor)
2021-09-16 8:21 ` Andrew Rybchenko
2021-09-17 0:43 ` Min Hu (Connor)
2021-10-30 9:59 ` Morten Brørup
2021-11-01 0:23 ` Min Hu (Connor)
2023-01-19 11:41 ` Ferruh Yigit
2023-01-19 16:45 ` Stephen Hemminger
2023-02-10 14:41 ` Ferruh Yigit
2023-03-23 14:40 ` Ferruh Yigit
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=29b75903-d212-c6e6-eedf-e3bc92ab816a@huawei.com \
--to=humin29@huawei.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=keith.wiles@intel.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).