All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qiming Yang <qiming.yang@intel.com>, dev@dpdk.org
Cc: jingjing.wu@intel.com, cunming.liang@intel.com
Subject: Re: [PATCH] net/i40e: fix link update delay
Date: Wed, 8 Feb 2017 15:37:48 +0000	[thread overview]
Message-ID: <0675b9b3-89ee-9f4b-ed54-89e4f47a1ecd@intel.com> (raw)
In-Reply-To: <cb6e8730-dab7-b635-3e89-df5e0afb524d@intel.com>

On 2/8/2017 3:30 PM, Ferruh Yigit wrote:
> On 2/8/2017 9:14 AM, Qiming Yang wrote:
>> This patch fixed the redundant delay in function link update. There is
>> no need to call rte_delay_ms and hold CPU for 100ms when link status is up.
>>
>> Fixes: 263333bbb7a9 ("i40e: fix link status timeout")
>>
>> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> 
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-02-08 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  9:14 [PATCH] net/i40e: fix link update delay Qiming Yang
2017-02-08 15:30 ` Ferruh Yigit
2017-02-08 15:37   ` 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=0675b9b3-89ee-9f4b-ed54-89e4f47a1ecd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=cunming.liang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=qiming.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.