DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yeddula, Avinash" <ayeddula@ciena.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Gajarampalli, Prasanth" <pgajaram@ciena.com>
Subject: [dpdk-dev] link state change not consistent (Flaps/stays DOWN/UP for ever)
Date: Tue, 22 Aug 2017 22:07:55 +0000	[thread overview]
Message-ID: <BN6PR04MB0594EA01B74D57828EFB9868D0840@BN6PR04MB0594.namprd04.prod.outlook.com> (raw)

Hi All,

With DPDK Stable 17.05 branch, we are seeing an issue with the link state of 10G ports on Broadwell.
Link status of one of the ports keeps flapping at regular intervals, typically starts after few seconds after the link appeared to settle down.
Other behaviors include not honoring a link state change set by the app. So far this is observed with ixgbe only, but have not yet explored if the issue is existing across drivers.
Also this issue was not seen with 16.11.2. Is this a known issue? If yes, are there any patches that can fix it?

Few patches (between 17.05 and 17.08) that were applied and not found any difference in behavior are below.

net/ixgbe: improve link state check on VF
In current implementation, when checking VF link state, PF state
is checked too, although the function has a parameter to tell
if PF state checking is needed.
But in some scenario, user may not care about the PF state.
This patch enables the unused parameter to only check the VF
link state.

net/ixgbe: fix LSC interrupt
If LSC flag is changed to off at last device start, the
enable flag is not cleared in HW.
This patch fixes it.

net/e1000: fix LSC interrupt
If LSC flag is changed to off at last device start, the
enable flag is not cleared in HW.
This patch fixes it.

ethdev: add deferred intermediate device state
This device state means that the device is managed externally, by
whichever party has set this state (PMD or application).

Note: this new device state is only an information. The related device
structure and operators are still valid and can be used normally.

It is however made private by device management helpers within ethdev,
making the device invisible to applications.

ethdev: count devices consistently
Make the rte_eth_dev_count() return the number of available devices even
after some are detached by the hotplug API or put in a deferred state.

net/ixgbe: fix Rx/Tx queue interrupt for x550 devices
x550 devices don't map interrupt vector before enabling Rx/Tx queue
interrupt.
Because of this interrupt mode is not working for x550 devices.

igb_uio: issue FLR during open and release of device file
Set UIO info device file operations open and release. Call pci reset
function inside open and release to clear device state at start and end.
Copied this behaviour from vfio_pci kernel module code. With this patch,
it is not mandatory to issue FLR by PMD's during init and close.

Bus master enable and disable are added in open and release respectively
to take care of device DMA.

ethdev: fix device state on detach
The device state should be handled by the ethdev layer when possible.
Applications should not have to do it.

Not setting the state to UNUSED will make the port_id of the device
valid for all ethdev API functions, usually resulting in segfault.

             reply	other threads:[~2017-08-22 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 22:07 Yeddula, Avinash [this message]
2017-08-23  0:46 ` Yeddula, Avinash

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=BN6PR04MB0594EA01B74D57828EFB9868D0840@BN6PR04MB0594.namprd04.prod.outlook.com \
    --to=ayeddula@ciena.com \
    --cc=dev@dpdk.org \
    --cc=pgajaram@ciena.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).