From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: dev <dev-bounces@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Helin" <helin.zhang@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] net/i40e: fix link status update
Date: Wed, 30 May 2018 09:54:47 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8C9975@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180530083047.33991-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org]
> Sent: Wednesday, May 30, 2018 9:31 AM
> To: dev@dpdk.org
> Cc: Zhang, Helin <helin.zhang@intel.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v3] net/i40e: fix link status update
>
> This patch fixes link status update problem in interrupt mode.
> Previously, directly reading link status register instead of accessing via admin
> queue command may cause the link status change interrupt callback inactive.
> This patch fixes the problem by making the driver only read the register in "no
> wait" and polling mode.
>
> Bugzilla ID: 54
> Fixes: eef2daf2e199 ("net/i40e: fix link update no wait")
> Cc: stable@dpdk.org
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Tested-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2018-05-30 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 16:23 [dpdk-dev] [PATCH] " Fan Zhang
2018-05-29 20:10 ` Thomas Monjalon
2018-05-30 8:26 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2018-05-30 8:30 ` Fan Zhang
2018-05-30 8:30 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2018-05-30 8:47 ` Zhang, Qi Z
2018-05-30 9:54 ` De Lara Guarch, Pablo [this message]
2018-05-30 10:25 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8977F8C9975@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev-bounces@dpdk.org \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stable@dpdk.org \
/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).