From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-ide@vger.kernel.org, "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: [PATCH 0/2][RFC] Make delay before debouncing configurable
Date: Fri, 25 Feb 2022 10:15:58 +0900 [thread overview]
Message-ID: <63ec50f7-8e21-3549-6c37-804863d38adc@opensource.wdc.com> (raw)
In-Reply-To: <7187af82-3d35-0094-f998-7d20bfc5192f@molgen.mpg.de>
On 2/24/22 23:34, Paul Menzel wrote:
[...]
>> Thank you for cooking this up. I tested this on the ASUS F2A85-M PRO
>> (AMD, 1022:0x7801), MSI B350M MORTAR (AMD, 1022:0x7901), and IBM S822LC
>> (Marvell, 1b4b:9235) with no issues and the expected decrease in boot time.
>
> There is still one issue I noticed. The MSI B350M MORTAR has nine(?)
> SATA ports, and only one is connected to an SSD. For some of the other
> unpopulated ports a delay of 100 ms happens (although in Linux kernel
> threads, but still in serial and not parallel). Unfortunately, that
> system uses LUKS encryption, and as things are happening in initrd, I do
> not know if the delays would hold up the overall boot. I need to do more
> tests.
>
> ```
> $ grep sata_link_hardreset 20220220-sata-hardreset.txt
> 0.706289 | 0) scsi_eh-70 | |
> sata_link_hardreset() {
> 0.718497 | 0) scsi_eh-92 | |
> sata_link_hardreset() {
> 0.728425 | 0) scsi_eh-92 | # 9927.978 us | } /*
> sata_link_hardreset */
> 0.811159 | 2) scsi_eh-70 | @ 104870.3 us | } /*
> sata_link_hardreset */
> 0.811329 | 2) scsi_eh-72 | |
> sata_link_hardreset() {
> 0.920672 | 3) scsi_eh-72 | @ 109343.5 us | } /*
> sata_link_hardreset */
> 0.920915 | 2) scsi_eh-78 | |
> sata_link_hardreset() {
> 1.024618 | 2) scsi_eh-78 | @ 103703.7 us | } /*
> sata_link_hardreset */
> 1.025027 | 0) scsi_eh-80 | |
> sata_link_hardreset() {
> 1.128589 | 0) scsi_eh-80 | @ 103561.6 us | } /*
> sata_link_hardreset */
> ```
This looks like the delay for the link stability check in
sata_link_debounce(). 100ms is added (more for hotplug case) to ensure
that the SStatus register DET field provides a stable value.
As mentioned in another email on this subject, I cannot find any text in
the AHCI and SATA IO specs that mandate such large delay. Still need to
dig the history of this delay and why it was added.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-02-25 1:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 15:46 [PATCH 0/2][RFC] Make delay before debouncing configurable Paul Menzel
2022-01-13 15:46 ` [PATCH 1/2] ata: Add module parameter `debounce_delay_ms` Paul Menzel
2022-01-13 15:46 ` [PATCH 2/2] ata: Warn about removal of debounce delay in Linux 5.19 Paul Menzel
2022-01-14 9:23 ` [PATCH 0/2][RFC] Make delay before debouncing configurable Damien Le Moal
2022-01-19 17:57 ` Robin H. Johnson
2022-01-20 0:14 ` Damien Le Moal
2022-02-14 7:09 ` Paul Menzel
2022-02-14 17:50 ` Robin H. Johnson
[not found] ` <7187af82-3d35-0094-f998-7d20bfc5192f@molgen.mpg.de>
2022-02-25 1:15 ` Damien Le Moal [this message]
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=63ec50f7-8e21-3549-6c37-804863d38adc@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robbat2@gentoo.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