DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Gregory Etelson <gregory@weka.io>
Cc: dev@dpdk.org, users@dpdk.org,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	wenzhuo.lu@intel.com, "Dai, Wei" <wei.dai@intel.com>
Subject: Re: [dpdk-dev] IXBGE VF: link state detection
Date: Wed, 24 May 2017 15:26:47 +0200	[thread overview]
Message-ID: <20170524152647.3499551d@platinum> (raw)
In-Reply-To: <8509342.3MbcxIPMKs@polaris>

Hi Gregory,

On Wed, 24 May 2017 12:50:19 +0300, Gregory Etelson <gregory@weka.io> wrote:
> Hello,
> 
> In my tests DPDK-17.05.0 process queries link state with rte_eth_link_get() each 50 msec
> during 5-20 MB/sec IOs flow.
> I turn Ethernet switch port down and up and check IXGBE VF PMD reaction to link state changes. 
> VF PMD correctly recognize link down events but may miss link up.
> When the fault occurs, subsequent calls to rte_eth_link_get will return link_status == 0 forever.
> I need to reset DPDK process to get correct link state value.
> My debugging shows that in case of the fault, mbx->ops.read(hw, &in_msg, 1, 0) in ixgbe_check_mac_link_vf
> keeps returning non-zero value

It looks there is at least one issue with
commit c12d22f65b13 ("net/ixgbe: ensure link status is updated")

Someone already complained about a problem related to the link status
on ixgbe (which is probably different than yours):
http://dpdk.org/ml/archives/dev/2017-May/066238.html

Anyway, maybe you can try to revert this patch and see if it
solves your issue?

Thanks
Olivier

  reply	other threads:[~2017-05-24 13:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  9:50 Gregory Etelson
2017-05-24 13:26 ` Olivier Matz [this message]
2017-05-25  3:48   ` Gregory Etelson
2017-05-25  0:56 ` Lu, Wenzhuo
2017-05-25  3:45   ` Gregory Etelson
2017-05-25  5:01     ` Lu, Wenzhuo
2017-05-25  5:22       ` Gregory Etelson
2017-05-25  5:44         ` Lu, Wenzhuo
2017-05-25  6:03           ` Gregory Etelson
2017-05-26  0:54             ` Lu, Wenzhuo
2017-05-26  4:25               ` Gregory Etelson

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=20170524152647.3499551d@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gregory@weka.io \
    --cc=users@dpdk.org \
    --cc=wei.dai@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).