From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Subject: cache flush support in SATA drives (was: Re: Questions about XFS)
Date: Thu, 29 Mar 2007 17:07:18 +0200 [thread overview]
Message-ID: <200703291707.18246.Martin@lichtvoll.de> (raw)
In-Reply-To: <20070317004731.GA5236@jdc.local>
Am Samstag 17 März 2007 schrieb Jason White:
> This might be slightly off-topic, but in choosing a SATA drive for a
> desktop machine, what features/standard-complaince should one look for
> in order to ensure that write barriers work? I know this involves
> flushing the drive cache, but is this support mandatory in any of the
> applicable standards?
Hello Jason!
I have no exact idea. I just now that dmesg usually tells you whether
cache flushes are supported.
But shouldn't modern SATA drives support NCQ anyway? Since NCQ doesn't
make any sense without the ability to flush the cache, I *think* any SATA
drive with NCQ support should do. NCQ support would allow the block layer
to offload the write barrier request ordering at least partly to the
device firmware.
"ii. For devices which have queue depth greater than 1 but don't
support ordered tags, block layer ensures that the requests preceding
a barrier request finishes before issuing the barrier request. Also,
it defers requests following the barrier until the barrier request is
finished. Older SCSI controllers/drives and SATA drives fall in this
category."
(Documentation/block/barrier.txt of Linux Kernel 2.6.20.4)
This also indicates that SATA drives should support NCQ.
Regards,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
prev parent reply other threads:[~2007-03-29 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 13:40 Questions about XFS clflush
2007-03-13 15:36 ` Klaus Strebel
2007-03-13 15:53 ` Stein M. Hugubakken
2007-03-13 15:55 ` Eric Sandeen
2007-03-14 16:33 ` Stewart Smith
2007-03-15 4:26 ` Taisuke Yamada
2007-03-15 9:07 ` clflush
2007-03-15 14:41 ` Geir A. Myrestrand
2007-03-16 10:36 ` Martin Steigerwald
2007-03-17 0:47 ` Jason White
2007-03-29 15:07 ` Martin Steigerwald [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=200703291707.18246.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-xfs@oss.sgi.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