From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "LEE,SCOTT " "(HP-Roseville,ex1)" <scott_lee@hp.com>
Cc: "'Jens Axboe'" <axboe@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ide write barriers
Date: 26 Feb 2003 23:10:11 +0000 [thread overview]
Message-ID: <1046301011.10600.4.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <6BD67FFB937FD411A04F00D0B74FE8780790C607@xrose06.rose.hp.com>
On Wed, 2003-02-26 at 21:20, LEE,SCOTT (HP-Roseville,ex1) wrote:
> If the cached writes can be reordered then of course it stands that caching
> would be unsafe. Does anyone know if IDE drives do this? I'm certainly no
> expert in this area but I thought only SCSI drives reordered operations.
Undefined. There certainly seem to be drives whose physical sector size
exceeds the one it presents to the world. Modern disk is all smoke and
mirrors for compatibility hack on top of compatibility hack.
I can't find anything in the spec that requires drives do not. Nor can
I find anything in the spec requiring a drive implements the cache flush
as anything except a nop [I believe ATA6 changed that for the very
newest stuff]. Not all drives appear to honour any kind of cache disable
either.
next prev parent reply other threads:[~2003-02-26 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 21:20 LEE,SCOTT (HP-Roseville,ex1)
2003-02-26 23:10 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 20:31 Scott Lee
2003-02-26 20:46 ` Jens Axboe
2003-02-27 21:57 ` Andre Hedrick
2003-02-05 15:18 Jens Axboe
2003-02-05 15:28 ` Marc-Christian Petersen
2003-02-05 16:33 ` Jens Axboe
2003-02-05 19:53 ` Marc-Christian Petersen
2003-02-06 9:26 ` Jens Axboe
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=1046301011.10600.4.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=scott_lee@hp.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
all inboxes | Powered by JetHome®