From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <lkml@rtr.ca>
Cc: Jens Axboe <axboe@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
"C.Y.M." <syphir@syphir.sytes.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Changes to ide-probe.c in 2.6.9-rc2 causing improper detection
Date: Tue, 14 Sep 2004 11:51:02 -0400 [thread overview]
Message-ID: <41471366.1070103@pobox.com> (raw)
In-Reply-To: <414710AA.80706@rtr.ca>
Mark Lord wrote:
> One obvious safeguard would be to never use FLUSH_CACHE on any
> drive that lacks UDMA, unless the drive claims to support FLUSH_CACHE.
>
> That will eliminate all current FLASH memory devices.
I think you're hunting for hueristics, not making a general rule. IMO
any assumption that this behavior will always be limited to flash
devices is a shaky assumption.
Your initial suggestion is probably much better:
> But one could augment it with a check of the ATA revision code,
> and possibly exclude drives that predate the *formal* introduction
> of the FLUSH_CACHE command, unless their IDENTIFY data specifically
> claims to include it.
That implies my code would become
if (ata version < 4)
return not-supported
if (wbcache-enabled or have-flush-cache or have-flush-cache-ext)
return supported
return not-supported
Yes?
Alan, do you still feel that the "wbcache-enabled" test should be removed?
Since wbcache-enabled is more of a hueristic than a formal test, I don't
mind removing it.
Jeff
next prev parent reply other threads:[~2004-09-14 15:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 2:26 Changes to ide-probe.c in 2.6.9-rc2 causing improper detection C.Y.M.
2004-09-14 6:06 ` Jens Axboe
2004-09-14 7:03 ` C.Y.M.
2004-09-14 7:06 ` Jens Axboe
2004-09-14 7:15 ` Jens Axboe
2004-09-14 8:20 ` C.Y.M.
2004-09-14 8:28 ` Jens Axboe
2004-09-14 10:09 ` Alan Cox
2004-09-14 11:12 ` Jens Axboe
2004-09-14 10:35 ` Alan Cox
2004-09-14 11:43 ` Jens Axboe
2004-09-14 11:19 ` Alan Cox
2004-09-14 12:21 ` Jens Axboe
2004-09-14 11:37 ` Gene Heskett
2004-09-14 10:07 ` Alan Cox
2004-09-14 11:11 ` Jens Axboe
2004-09-14 11:59 ` Bartlomiej Zolnierkiewicz
2004-09-14 13:15 ` Jens Axboe
2004-09-14 10:05 ` Alan Cox
2004-09-14 11:09 ` Jens Axboe
2004-09-14 12:07 ` Bartlomiej Zolnierkiewicz
2004-09-14 15:18 ` Jeff Garzik
2004-09-14 15:25 ` Jens Axboe
2004-09-14 15:05 ` Alan Cox
2004-09-14 15:33 ` Mark Lord
2004-09-14 15:39 ` Mark Lord
2004-09-14 15:51 ` Jeff Garzik [this message]
2004-09-14 15:06 ` Alan Cox
2004-09-14 15:45 ` Jeff Garzik
2004-09-14 15:31 ` Mark Lord
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=41471366.1070103@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=syphir@syphir.sytes.net \
/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