From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-ide@vger.kernel.org
Subject: SATA: Is "DPO and FUA" ever supported?
Date: Thu, 21 Jun 2007 17:30:02 +0400 [thread overview]
Message-ID: <467A7D5A.9070009@msgid.tls.msk.ru> (raw)
On each and every machine out there, and on every dmesg
output posted on numerous mailinglists, I see messages
similar to this:
scsi 0:0:0:0: Direct-Access ATA ST3250620NS 3.AE PQ: 0 ANSI: 5
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
for SATA disk drives. And I wonder -- are those features
supported at all by linux, and/or are there disk drives
out there which supports it as well?
For my Seagate ST3250620NS SATA drive (it's a "server" drive,
whatever it means), I can see -- at least --
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
reported by hdparm -I. I wonder what "FLUSH CACHE EXT" means,
and whenever it can be used to support DPO and/or FUA...
Thanks.
/mjt
next reply other threads:[~2007-06-21 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 13:30 Michael Tokarev [this message]
2007-06-22 14:15 ` SATA: Is "DPO and FUA" ever supported? Sergei Shtylyov
2007-06-22 14:57 ` Sergei Shtylyov
2007-07-03 7:10 ` Tejun Heo
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=467A7D5A.9070009@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).