From: "Coulson, Ken" <kcoulson@ciena.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] problem with continual link status down events
Date: Thu, 1 Sep 2016 18:51:46 -0400 [thread overview]
Message-ID: <D3EDFF11.BF71%kcoulson@ciena.com> (raw)
I am seeing a problem with link state change using interrupts using a Broadwell
with on-board 10G-BaseT LAN ports (0x15AD) running DPDK 16.04. There is an Ixia
connected to the two 10G ports and both are initially up. One of the
connections is brought down via the Ixia and the software gets a single down
event through the callback installed with rte_eth_dev_callback_register() and
enabling lsc in the rte_eth_conf structure. The connection is then re-enabled
and a single up event is received as expected. However on the other 10G port
when the connection is brought down sporadic down events are continually
received at a frequency ranging from about 1 seconds to 20 seconds.
I do not see the problem with the two 1G ports. The problem has been
seen on two different Broadwell boxes.
I'm looking for information from others that have seen anything like this problem.
Ken Coulson
Software Engineer with Ciena
reply other threads:[~2016-09-01 22:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=D3EDFF11.BF71%kcoulson@ciena.com \
--to=kcoulson@ciena.com \
--cc=dev@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).