From: Graham Whyte <grwhyte@linux.microsoft.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-pci@vger.kernel.org, shyamsaini@linux.microsoft.com,
code@tyhicks.com, Okaya@kernel.org, bhelgaas@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Reduce delay after FLR of Microsoft MANA devices
Date: Fri, 30 May 2025 09:26:16 -0700 [thread overview]
Message-ID: <b23fb8f4-0da7-4403-8a2d-665d5675be9c@linux.microsoft.com> (raw)
In-Reply-To: <aDg4PE4Zbzwps71E@wunner.de>
On 5/29/2025 3:34 AM, Lukas Wunner wrote:
> On Wed, May 28, 2025 at 06:10:47PM +0000, grwhyte@linux.microsoft.com wrote:
>> Add a device-specific reset for Microsoft MANA devices with the FLR
>> delay reduced from 100ms to 10ms. While this is not compliant with the pci
>> spec, these devices safely complete the FLR much quicker than 100ms and
>> this can be reduced to optimize certain scenarios
>
> How often do you reset these devices that 90 msec makes a difference?
> What are these "certain scenarios"?
>
VF removal and rescan is the main scenario for runtime repairs and driver updates.
Doing this on scale with 100ms adds up to significant time across multiple VFs.
> There are already "d3hot_delay" and "d3cold_delay" members in
> struct pci_dev. I'm wondering if it would make sense to add
> another one, say, "flr_delay". That would allow other devices
> to reduce or lengthen the delay without each of them having to
> duplicate pcie_flr(). The code duplication makes this difficult
> to maintain long-term.
>
This is a good suggestion, we can make this more generic.
> Thanks,
>
> Lukas
next prev parent reply other threads:[~2025-05-30 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 18:10 [PATCH v2] PCI: Reduce delay after FLR of Microsoft MANA devices grwhyte
2025-05-29 10:34 ` Lukas Wunner
2025-05-30 16:26 ` Graham Whyte [this message]
2025-05-31 14:09 ` Lukas Wunner
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=b23fb8f4-0da7-4403-8a2d-665d5675be9c@linux.microsoft.com \
--to=grwhyte@linux.microsoft.com \
--cc=Okaya@kernel.org \
--cc=bhelgaas@google.com \
--cc=code@tyhicks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=shyamsaini@linux.microsoft.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