From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Miskell, Timothy" <timothy.miskell@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Tsai, Jonathan1" <jonathan1.tsai@intel.com>
Subject: RE: [PATCH v2] net/ice: fix L1 check interval to account for longer link times
Date: Fri, 20 Oct 2023 01:14:45 +0000 [thread overview]
Message-ID: <DM4PR11MB5994F689B07F3B46DFB9407CD7DBA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231019172610.325081-1-timothy.miskell@intel.com>
> -----Original Message-----
> From: Miskell, Timothy <timothy.miskell@intel.com>
> Sent: Friday, October 20, 2023 1:26 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Miskell, Timothy <timothy.miskell@intel.com>; Tsai,
> Jonathan1 <jonathan1.tsai@intel.com>
> Subject: [PATCH v2] net/ice: fix L1 check interval to account for longer link
> times
>
> For edge cases where the transceiver is physically inserted first and
> immediately afterwards the DPDK PF is started the LSC event may occur
> outside the current setting for the maximum check interval window. This
> change lengthens the check interval to account for this along with other
> reported cases where the link event may be longer than 1 second.
Fixes: cf911d90e366 ("net/ice: support link update")
Cc: stable@dpdk.org
>
> Signed-off-by: Timothy Miskell <timothy.miskell@intel.com>
> Tested-by: Jonathan Tsai <jonathan1.tsai@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2023-10-20 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 17:26 Timothy Miskell
2023-10-20 1:14 ` Zhang, Qi Z [this message]
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=DM4PR11MB5994F689B07F3B46DFB9407CD7DBA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jonathan1.tsai@intel.com \
--cc=timothy.miskell@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).