[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180807.124448.1502585319140215353.davem@davemloft.net>
Date: Tue, 07 Aug 2018 12:44:48 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mr.nuke.me@...il.com
Cc: linux-pci@...r.kernel.org, bhelgaas@...gle.com,
jakub.kicinski@...ronome.com, keith.busch@...el.com,
alex_gagniuc@...lteam.com, austin_bolen@...l.com,
shyam_iyer@...l.com, ariel.elior@...ium.com,
everest-linux-l2@...ium.com, michael.chan@...adcom.com,
ganeshgr@...lsio.com, jeffrey.t.kirsher@...el.com,
tariqt@...lanox.com, saeedm@...lanox.com, leon@...nel.org,
dirk.vandermerwe@...ronome.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
linux-rdma@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH v6 1/9] PCI: Check for PCIe downtraining conditions
From: Alexandru Gagniuc <mr.nuke.me@...il.com>
Date: Mon, 6 Aug 2018 18:25:35 -0500
> PCIe downtraining happens when both the device and PCIe port are
> capable of a larger bus width or higher speed than negotiated.
> Downtraining might be indicative of other problems in the system, and
> identifying this from userspace is neither intuitive, nor
> straightforward.
>
> The easiest way to detect this is with pcie_print_link_status(),
> since the bottleneck is usually the link that is downtrained. It's not
> a perfect solution, but it works extremely well in most cases.
>
> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@...il.com>
Feel free to merge this entire series via the PCI tree.
For the series:
Acked-by: David S. Miller <davem@...emloft.net>
Powered by blists - more mailing lists