From: 韩爽 <hanshuang@qianxin.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Mingjin Ye <mingjinx.ye@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"yidingx.zhou@intel.com" <yidingx.zhou@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Mingjin Ye <mingjinx.ye@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>
Subject: Re: [PATCH] net/ice: fix get link status timeout
Date: Mon, 6 Feb 2023 07:56:44 +0000 [thread overview]
Message-ID: <a556e420c56b4469b5a0cc13d6f681b0@qianxin.com> (raw)
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, February 06, 2023 3:23 PM
> To: Mingjin Ye <mingjinx.ye@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; yidingx.zhou@intel.com; Qiming Yang
> <qiming.yang@intel.com>; Qi Zhang <qi.z.zhang@intel.com>; Mingjin Ye
> <mingjinx.ye@intel.com>; david.marchand@redhat.com;
> ferruh.yigit@amd.com
> Subject: Re: [PATCH] net/ice: fix get link status timeout
>
> 06/02/2023 07:22, Mingjin Ye:
> > When hw is just started, it will immediately obtain the link status,
> > and the longest attempt is 1 second. Some NICs are slow to initialize,
> > which make it fails to obtain the link status.
> >
> > The patch fixes this issue by modifying the longest attempt to 5 seconds.
>
> What is the consequence?
> In which case, DPDK application would be blocked during 5 seconds?
>
I think ice_link_update with wait_to_complete needs to be optimized when ice_link_update.
Our system integrates dozens or more interfaces(E810), even if wait 1 second, the system starts very slowly.
next reply other threads:[~2023-02-06 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 7:56 韩爽 [this message]
2023-02-06 10:51 ` Ye, MingjinX
2023-02-07 6:48 ` Yang, Qiming
-- strict thread matches above, loose matches on Subject: below --
2023-02-06 8:35 Shuang Han
2023-02-06 6:22 Mingjin Ye
2023-02-06 7:23 ` Thomas Monjalon
2023-02-06 8:14 ` Ye, MingjinX
2023-02-06 9:15 ` Thomas Monjalon
2023-02-06 10:06 ` Ye, MingjinX
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=a556e420c56b4469b5a0cc13d6f681b0@qianxin.com \
--to=hanshuang@qianxin.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mingjinx.ye@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yidingx.zhou@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).