From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/hns3: support wait to complete in link update API
Date: Thu, 8 Apr 2021 15:35:05 +0100 [thread overview]
Message-ID: <d6a17655-8ac2-3ef2-4795-56e79235df05@intel.com> (raw)
In-Reply-To: <1617108805-9096-1-git-send-email-humin29@huawei.com>
On 3/30/2021 1:53 PM, Min Hu (Connor) wrote:
> From: Huisong Li <lihuisong@huawei.com>
>
> There are two APIs in ethdev layer to get link status of device, namely,
> "rte_eth_link_get" and "rte_eth_link_get_nowait". When the device link
> is unstable or auto-negotiation is in progress, the first API supports
> the function of waiting for the NIC to link up, and the maximum waiting
> time is 9 seconds based on DPDK Documentation. For the hns3 PMD driver,
> the link can be established within 2 seconds.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-04-08 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 12:53 Min Hu (Connor)
2021-04-08 14:35 ` Ferruh Yigit [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=d6a17655-8ac2-3ef2-4795-56e79235df05@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@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).