From: Mark Lord <lkml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Todd Poynor <tpoynor@mvista.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tim.bird@am.sony.com, dsingleton@mvista.com
Subject: Re: [PATCH] Configure IDE probe delays
Date: Tue, 03 Aug 2004 13:47:06 -0400 [thread overview]
Message-ID: <410FCF9A.0@rtr.ca> (raw)
In-Reply-To: <410AEDC8.6030901@pobox.com>
I'm the dude responsible for the infamous "50 milliseconds" here.
I agree that (1) it is overkill, (2) it could be optimised,
and (3) it is very very non-standard.
But it also works extraordinarilly well. I still am very active
with ATA and SATA driver development, and the basic Linux IDE probe
works for me on vendor hardware where their own standards-specific
routines sometimes fail (even in their windows drivers).
If possible, it would be best to let it be, and over time it will
be less and less important as SATA and kin take over the universe.
Every time I tried to tweak it to be faster, it seemed to break
some system or another.
One possibility here would be to augment it with reset signature probing,
and/or a cyl-high read/write test. These could speed things up for
more mainstream cases. But I'm not going to touch what's there myself!
Cheers
--
Mark Lord
(hdparm keeper & the original "Linux IDE Guy")
next prev parent reply other threads:[~2004-08-03 17:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 19:11 [PATCH] Configure IDE probe delays Todd Poynor
2004-07-30 21:36 ` Lee Revell
2004-07-30 22:35 ` Alan Cox
2004-07-31 0:12 ` Lee Revell
[not found] ` <200407311434.59604.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-31 18:00 ` Lee Revell
2004-08-27 17:45 ` Greg Stark
2004-08-27 17:53 ` Lee Revell
2004-08-27 18:05 ` Bartlomiej Zolnierkiewicz
2004-08-27 18:08 ` Lee Revell
2004-08-27 18:59 ` Bartlomiej Zolnierkiewicz
2004-09-01 13:20 ` Mark Lord
2004-09-01 14:43 ` Jeff Garzik
2004-09-01 15:30 ` Mark Lord
2004-09-01 15:36 ` Mark Lord
2004-09-01 19:36 ` Lee Revell
2004-09-01 18:42 ` Alan Cox
2004-09-01 15:06 ` Alan Cox
2004-09-01 19:08 ` Lee Revell
2004-09-02 16:04 ` Mark Lord
2004-09-01 15:40 ` Bartlomiej Zolnierkiewicz
2004-07-31 18:06 ` Lee Revell
2004-07-31 19:35 ` Alan Cox
2004-07-31 21:35 ` Lee Revell
2004-07-31 21:44 ` Jeff Garzik
2004-07-31 22:12 ` Lee Revell
2004-08-04 17:30 ` Anthony de Boer
2004-08-05 21:39 ` Tim Bird
2004-07-31 0:54 ` Jeff Garzik
2004-08-03 17:47 ` Mark Lord [this message]
2004-08-06 15:48 ` Jeff Garzik
2004-08-06 19:29 ` Tim Bird
2004-08-06 20:46 ` Todd Poynor
2004-08-02 21:56 ` Tim Bird
2004-08-02 21:01 ` Alan Cox
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=410FCF9A.0@rtr.ca \
--to=lkml@rtr.ca \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dsingleton@mvista.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
--cc=tpoynor@mvista.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