From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] drivers/i40e: fix link update no wait
Date: Fri, 9 Mar 2018 13:22:28 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71ADB3A36@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B749EDA@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: Lu, Wenzhuo
> Sent: Friday, March 9, 2018 4:45 PM
> To: Zhang, Roy Fan; dev@dpdk.org
> Cc: Glynn, Michael J; Zhang, Roy Fan; stable@dpdk.org; Zhang, Helin; Liang,
> Cunming; Chilikin, Andrey
> Subject: RE: [dpdk-dev] [PATCH v2] drivers/i40e: fix link update no wait
>
> Hi,
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fan Zhang
> > Sent: Thursday, March 8, 2018 8:18 PM
> > To: dev@dpdk.org
> > Cc: Glynn, Michael J <michael.j.glynn@intel.com>; Zhang, Roy Fan
> > <roy.fan.zhang@intel.com>; stable@dpdk.org; Zhang, Helin
> > <helin.zhang@intel.com>; Liang, Cunming <cunming.liang@intel.com>;
> > Chilikin, Andrey <andrey.chilikin@intel.com>
> > Subject: [dpdk-dev] [PATCH v2] drivers/i40e: fix link update no wait
> >
> > Fixes: 263333bbb7a9 ("i40e: fix link status timeout")
> > Cc: cunming.liang@intel.com
> > Cc: stable@dpdk.org
> >
> > In i40e_dev_link_update() the driver obtains the link status info via
> > admin queue command despite of "no_wait" flag. This requires
> > relatively long time and may be a problem to some application such as
> > ovs-dpdk (https://bugzilla.redhat.com/show_bug.cgi?id=1551761).
> >
> > This patch aims to fix the problem by using a different approach of
> > obtaining link status for i40e NIC without waiting.
> > Instead of getting the link status via admin queue command, this patch
> > reads the link status registers to accelerate the procedure.
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net-intel, with minor commit log changes. Thanks!
/Helin
prev parent reply other threads:[~2018-03-09 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 11:55 [dpdk-dev] [PATCH] " Fan Zhang
2018-03-08 12:17 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2018-03-08 13:01 ` Eelco Chaudron
2018-03-09 8:45 ` Lu, Wenzhuo
2018-03-09 13:22 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E71ADB3A36@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@intel.com \
--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).