From: sashiko-bot@kernel.org
To: "Ferran Duarri" <ferran.duarri@me.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI/sysfs: document the link speed and width attributes
Date: Thu, 20 Aug 2026 20:06:47 +0000 [thread overview]
Message-ID: <20260820200648.200BB1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820200359.283335-1-ferran.duarri@me.com>
> max_link_speed, max_link_width, current_link_speed and current_link_width
> have been exported under /sys/bus/pci/devices/.../ since 2018, by
> commit 56c1af4606f0 ("PCI: Add sysfs max_link_speed/width, current_link_speed/width, etc"),
> and none of the four appear anywhere in Documentation/ABI.
>
> The gap matters most for current_link_speed. current_link_speed_show()
> performs a fresh PCI_EXP_LNKSTA read on every open, so the value reflects
> the link state at that instant. Modern GPUs retrain their link continuously
> as part of idle power management, which means a single read can legitimately
> return any speed the link supports, not the speed the link will use under
> load.
>
> Observed on an RTX 5070 in a PCIe 4.0 x16 slot, same boot, no configuration
> change between the two reads: 5.0 GT/s while idle, 16.0 GT/s under load.
> Comparing current_link_speed against max_link_speed at idle is therefore not
> [ ... ]
> end's capability rather than the link's.
>
> No functional change.
>
> Signed-off-by: Ferran Duarri <ferran.duarri@me.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260820200359.283335-1-ferran.duarri@me.com?part=1
next prev parent reply other threads:[~2026-08-20 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:42 [PATCH] PCI/sysfs: document the link speed and width attributes Ferran Duarri
2026-08-20 18:50 ` sashiko-bot
2026-08-20 19:53 ` [PATCH v2] " Ferran Duarri
2026-08-20 19:56 ` sashiko-bot
2026-08-20 20:03 ` Ferran Duarri
2026-08-20 20:06 ` sashiko-bot [this message]
2026-08-21 4:31 ` Greg KH
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=20260820200648.200BB1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ferran.duarri@me.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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