From: "Min Hu (Connor)" <humin29@huawei.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org
Cc: <ferruh.yigit@intel.com>, <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [RFC] ethdev: improve link speed to string
Date: Mon, 1 Nov 2021 08:23:47 +0800 [thread overview]
Message-ID: <2a7361aa-962e-3491-4286-c2968467bdf0@huawei.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D86C81@smartserver.smartshare.dk>
在 2021/10/30 17:59, Morten Brørup 写道:
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Min Hu (Connor)
>> Sent: Friday, 17 September 2021 02.44
>>
>> Agree with you. Thanks Andrew
>>
>> 在 2021/9/16 16:21, Andrew Rybchenko 写道:
>>> On 9/16/21 11:16 AM, Min Hu (Connor) wrote:
>>>> Hi, Andrew,
>>>>
>>>> 在 2021/9/16 14:22, Andrew Rybchenko 写道:
>>>>> On 9/16/21 5:56 AM, Min Hu (Connor) wrote:
>>>>>> Currently, link speed to string only supports specific speeds,
>> like 10M,
>>>>>> 100M, 1G etc.
>>>>>>
>>>>>> This patch expands support for any link speed which is over 1M and
>> one
>>>>>> decimal place will kept for display at most.
>>>>>>
>>>>>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>>>>>> ---
>>>>>> lib/ethdev/rte_ethdev.c | 34 +++++++++++++++++-----------------
>>>>>> 1 file changed, 17 insertions(+), 17 deletions(-)
>>>>>>
>>>>>> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
>>>>>> index daf5ca9242..1d3b960305 100644
>>>>>> --- a/lib/ethdev/rte_ethdev.c
>>>>>> +++ b/lib/ethdev/rte_ethdev.c
>>>>>> @@ -2750,24 +2750,24 @@ rte_eth_link_get_nowait(uint16_t port_id,
>>>>>> struct rte_eth_link *eth_link)
>>>>>> const char *
>>>>>> rte_eth_link_speed_to_str(uint32_t link_speed)
>>>>>> {
>>>>>> - switch (link_speed) {
>>>>>> - 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";
>>>>>> +#define SPEED_STRING_LEN 16
>>>>>> + static char name[SPEED_STRING_LEN];
>>>>>
>>>>> NACK
>>>>>
>>>>> Nothing good will happen if you try to use the function to
>>>>> print two different link speeds in one log message.
>>>> You are right.
>>>> And use malloc for "name" will result in memory leakage, which is
>> also
>>>> not a good option.
>>>>
>>>> BTW, do you think if we need to modify the function
>>>> "rte_eth_link_speed_to_str"?
>>>
>>> IMHO it would be more pain than gain in this case.
>
> If ETH_SPEED_NUM_xyz values was an enum instead of #define, the default case could be removed from this switch, and the compiler would emit a warning if a new ETH_SPEED_NUM_xyz was introduced without adding a case for it in this function.
But, according to some coding standard, default case should be added in
"switch case" syntax.
>
> -Morten
>
next prev parent reply other threads:[~2021-11-01 0:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 8:45 [dpdk-dev] Questions about rte_eth_link_speed_to_str API Min Hu (Connor)
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) [this message]
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=2a7361aa-962e-3491-4286-c2968467bdf0@huawei.com \
--to=humin29@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mb@smartsharesystems.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).