DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Li, Xiaoyun" <xiaoyun.li@intel.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: add link speed check before port start
Date: Fri, 30 Apr 2021 04:46:40 +0000	[thread overview]
Message-ID: <DM4PR11MB5534E4CF005D252B210DE676995E9@DM4PR11MB5534.namprd11.prod.outlook.com> (raw)
In-Reply-To: <95042d3b-408a-a290-de18-a887de558555@huawei.com>



> -----Original Message-----
> From: Huisong Li <lihuisong@huawei.com>
> Sent: Friday, April 30, 2021 12:04
> To: Li, Xiaoyun <xiaoyun.li@intel.com>
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: add link speed check
> before port start
> 
> 
> 在 2021/4/30 11:19, Li, Xiaoyun 写道:
> >> -----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.
> > I guess it's because if it's not supported speed, it will just be UNKNOWN and
> user can config again?
> 
> I think that the validity of the configuration delivered by dev_configure is
> ensured by this interface and cannot be left to the backend.
> 
> Because it facilitates users to handle abnormal configurations in a timely
> manner. It may be more appropriate for the driver to do this check in
> dev_configure.

I still think it's not necessary.

> 
> In addition, even if other drivers do not add this check in dev_configure, this
> patch does not seem to affect the current behavior of these drivers.
> 
> > BTW, even if this behavior is accepted by others, still some comments below.
> >
> >> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> >> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> >> ---
> >>   app/test-pmd/cmdline.c | 42
> >> ++++++++++++++++++++++++++++++++++++++++-
> >> -
> >>   1 file changed, 40 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c index
> >> 5fdcc1c..ddbc629 100644
> >> --- a/app/test-pmd/cmdline.c
> >> +++ b/app/test-pmd/cmdline.c
> >> @@ -1549,8 +1549,12 @@ cmd_config_speed_all_parsed(void
> *parsed_result,
> >>   			__rte_unused void *data)
> >>   {
> >>   	struct cmd_config_speed_all *res = parsed_result;
> >> +	uint32_t old_link_speeds[RTE_MAX_ETHPORTS];
> >> +	struct rte_port *port;
> >>   	uint32_t link_speed;
> >>   	portid_t pid;
> >> +	portid_t i;
> >> +	int ret;
> >>
> >>   	if (!all_ports_stopped()) {
> >>   		printf("Please stop all ports first\n"); @@ -1562,7 +1566,26 @@
> >> cmd_config_speed_all_parsed(void *parsed_result,
> >>   		return;
> >>
> >>   	RTE_ETH_FOREACH_DEV(pid) {
> >> -		ports[pid].dev_conf.link_speeds = link_speed;
> >> +		port = &ports[pid];
> >> +		old_link_speeds[pid] = port->dev_conf.link_speeds;
> >> +		port->dev_conf.link_speeds = link_speed;
> >> +		ret = rte_eth_dev_configure(pid, nb_rxq, nb_txq,
> >> +					    &port->dev_conf);
> >> +		if (ret < 0) {
> >> +			printf("Failed to check link speeds for port %d, ret
> >> = %d.\n",
> >> +				pid, ret);
> >> +			goto roolback;
> > Why don't you just add restoring all ports speed here and then "break"? No
> matter one dev fails or not, all ports will do reconfig from your code logic.
> > And you type rollback wrongly.
> 
> It cannot exit directly after restoring all ports speed. If the cmd fails to execute,
> it is necessary to reconfigure device with the correct configuration.
>   Because "nb_rx/tx_queues" in dev->data are cleared to zero if dev_configure
> fails to be executed in PMD driver.

?
cmd_reconfig_device_queue(RTE_PORT_ALL, 1, 1); is at the end of this cmd. This will re-config all ports.
I don't understand why can't you add a restoring in this if and break this loop and do this reconfig.

> 
> >> +		}
> >> +	}
> >> +
> >> +	cmd_reconfig_device_queue(RTE_PORT_ALL, 1, 1);
> >> +
> >> +	return;
> >> +
> >> +roolback:
> >> +	for (i = 0; i <= pid; i++) {
> >> +		port = &ports[i];
> >> +		port->dev_conf.link_speeds = old_link_speeds[i];
> >>   	}
> >>
> >>   	cmd_reconfig_device_queue(RTE_PORT_ALL, 1, 1); @@ -1621,7
> >> +1644,10 @@ cmd_config_speed_specific_parsed(void *parsed_result,
> >>   				__rte_unused void *data)
> >>   {
> >>   	struct cmd_config_speed_specific *res = parsed_result;
> >> +	uint32_t old_link_speeds;
> >> +	struct rte_port *port;
> >>   	uint32_t link_speed;
> >> +	int ret;
> >>
> >>   	if (!all_ports_stopped()) {
> >>   		printf("Please stop all ports first\n"); @@ -1635,8 +1661,20 @@
> >> cmd_config_speed_specific_parsed(void *parsed_result,
> >>   			&link_speed) < 0)
> >>   		return;
> >>
> >> -	ports[res->id].dev_conf.link_speeds = link_speed;
> >> +	port = &ports[res->id];
> >> +	old_link_speeds = port->dev_conf.link_speeds;
> >> +	port->dev_conf.link_speeds = link_speed;
> >> +	ret = rte_eth_dev_configure(res->id, nb_rxq, nb_txq,
> >> +				    &port->dev_conf);
> >> +	if (ret < 0) {
> >> +		printf("Failed to check link speeds for port %d, ret = %d.\n",
> >> +			res->id, ret);
> >> +		port->dev_conf.link_speeds = old_link_speeds;
> >> +	}
> >>
> >> +	/*
> >> +	 * If the cmd fails to execute, it is necessary to reconfigure device.
> >> +	 */
> >>   	cmd_reconfig_device_queue(RTE_PORT_ALL, 1, 1);  }
> >>
> >> --
> >> 2.7.4
> > .

  reply	other threads:[~2021-04-30  4:47 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 [this message]
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
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=DM4PR11MB5534E4CF005D252B210DE676995E9@DM4PR11MB5534.namprd11.prod.outlook.com \
    --to=xiaoyun.li@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lihuisong@huawei.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).