DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: dev <dev-bounces@dpdk.org>, "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Matthew Smith <mgsmith@netgate.com>
Subject: Re: [dpdk-dev] [PATCH] ixgbe: wait longer for link after fiber MAC setup
Date: Sun, 30 Sep 2018 02:15:57 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611532A8354@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180716163604.31896-1-mgsmith@netgate.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org]
> Sent: Tuesday, July 17, 2018 12:36 AM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Matthew Smith <mgsmith@netgate.com>
> Subject: [dpdk-dev] [PATCH] ixgbe: wait longer for link after fiber MAC setup
> 
> After setting up the link on a fiber port, the maximum wait time for the link to
> come up is 500 ms in ixgbe_setup_mac_link_multispeed_fiber().
> On an x550 SFP+ port, this is often not sufficiently long for the link to come up.
> This can result in never being able to retrieve accurate link status for the port
> using rte_eth_link_get_nowait().
> 
> Increase the maximum wait time in ixgbe_setup_mac_link_multispeed_fiber()
> to 1 s.
> 
> Bugzilla ID: 69
> Fixes: f3430431abaf ("ixgbe/base: add SFP+ dual-speed support")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Matthew Smith <mgsmith@netgate.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

      reply	other threads:[~2018-09-30  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 16:36 Matthew Smith
2018-09-30  2:15 ` 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=039ED4275CED7440929022BC67E70611532A8354@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev-bounces@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=mgsmith@netgate.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@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).