From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: add link speed check before port start
Date: Tue, 8 Jun 2021 13:34:40 +0300 [thread overview]
Message-ID: <12f1a7fa-a1b9-6f6c-098d-9cf499478a1f@oktetlabs.ru> (raw)
In-Reply-To: <DM4PR11MB5534C69344AE62FCC5538A13995E9@DM4PR11MB5534.namprd11.prod.outlook.com>
On 4/30/21 6:19 AM, Li, Xiaoyun wrote:
>
>> -----Original Message-----
>> From: Min Hu (Connor) <humin29@huawei.com>
>> Sent: Wednesday, April 28, 2021 16:37
>> To: dev@dpdk.org
>> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Li, Xiaoyun <xiaoyun.li@intel.com>
>> Subject: [PATCH v2 1/2] app/testpmd: add link speed check before port start
>>
>> From: Huisong Li <lihuisong@huawei.com>
>>
>> Currently, to check whether the configured link_speeds is valid, we have to run
>> "port start". In addition, if the configuration fails, "port->dev_conf.link_speeds"
>> maintained in testpmd cannot be restored.
>>
>> This patch adds the link_speeds check before port start by calling dev_configure,
>> and resolves these problems.
>
> Not sure about this patch. I don't think you can fix the issue you mentioned.
> Probably only hns3 does speed check in dev_configure. I don't see this in other drivers, not in i40e/ice/mlx.
The configuration check may be done by passing the
configuration to HW and HW may reject it.
(Just as a side note that it is not that simple/)
> I guess it's because if it's not supported speed, it will just be UNKNOWN and user can config again?
>
> BTW, even if this behavior is accepted by others, still some comments below.
>
[snip]
next prev parent reply other threads:[~2021-06-08 10:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 6:21 [dpdk-dev] [PATCH 0/2] fixes for link speed Min Hu (Connor)
2021-04-19 6:21 ` [dpdk-dev] [PATCH 1/2] app/testpmd: add link speed check before port start Min Hu (Connor)
2021-04-20 12:11 ` Ferruh Yigit
2021-04-21 3:44 ` Min Hu (Connor)
2021-04-19 6:21 ` [dpdk-dev] [PATCH 2/2] app/testpmd: fix link speed for a specified port Min Hu (Connor)
2021-04-19 22:52 ` Ferruh Yigit
2021-04-28 8:36 ` [dpdk-dev] [PATCH v2 0/2] fixes for link speed Min Hu (Connor)
2021-04-28 8:36 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: add link speed check before port start Min Hu (Connor)
2021-04-30 3:19 ` Li, Xiaoyun
2021-04-30 4:04 ` Huisong Li
2021-04-30 4:46 ` Li, Xiaoyun
2021-05-04 1:46 ` Huisong Li
2021-05-06 2:36 ` Li, Xiaoyun
2021-05-06 6:46 ` Huisong Li
2021-06-08 10:34 ` Andrew Rybchenko [this message]
2021-06-08 10:49 ` Andrew Rybchenko
2021-06-10 6:13 ` Huisong Li
2021-04-28 8:36 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: fix link speed for a specified port Min Hu (Connor)
2021-04-29 8:42 ` Li, Xiaoyun
2021-07-02 10:02 ` Andrew Rybchenko
2021-06-08 10:29 ` [dpdk-dev] [PATCH v2 0/2] fixes for link speed Andrew Rybchenko
2021-06-10 6:19 ` Huisong Li
2021-06-28 3:25 ` Min Hu (Connor)
2021-06-29 6:24 ` Singh, Aman Deep
2021-06-29 7:31 ` Min Hu (Connor)
2021-07-02 10:05 ` Andrew Rybchenko
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=12f1a7fa-a1b9-6f6c-098d-9cf499478a1f@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=xiaoyun.li@intel.com \
/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).