From: Stephen Hemminger <stephen@networkplumber.org>
To: lew@perftech.com
Cc: dev@dpdk.org
Subject: Re: [PATCH] ixgbe: Removed FreeBSD forcing wait in ixgbe_dev_link_update_share()
Date: Tue, 22 Oct 2024 08:34:55 -0700 [thread overview]
Message-ID: <20241022083455.65cbfb9a@hermes.local> (raw)
In-Reply-To: <20241022144205.49664-1-lew@perftech.com>
On Tue, 22 Oct 2024 09:42:05 -0500
lew@perftech.com wrote:
> From: Lewis Donzis <lew@perftech.com>
>
> Forcing wait true prevents checking link status without delay, because the function will wait more than 10 seconds for link status to be true.
>
> Signed-off-by: Lewis Donzis <lew@perftech.com>
A little concerned that original patch was trying to address a problem.
Fixes: 0012111a3d87 ("net/ixgbe: fix link status synchronization on BSD")
next prev parent reply other threads:[~2024-10-22 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 14:42 lew
2024-10-22 15:34 ` Stephen Hemminger [this message]
2024-10-22 15:58 ` Lewis Donzis
2024-10-22 16:16 ` Stephen Hemminger
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=20241022083455.65cbfb9a@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=lew@perftech.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).