linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA: Is "DPO and FUA" ever supported?
Date: Fri, 22 Jun 2007 18:15:08 +0400	[thread overview]
Message-ID: <467BD96C.4090005@ru.mvista.com> (raw)
In-Reply-To: <467A7D5A.9070009@msgid.tls.msk.ru>

Hello.

Michael Tokarev wrote:

> 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?

    Don't know, the bits have just quite recently been included into ATA spec, 
IIRC...

> 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,

    It reports LBA48 of a failing sector while FLUSH CACHE can only report LBA28.

> and whenever it can be used to support DPO and/or FUA...

    DPO and FUA bits are a part of SCSI CDB and so only affect the block range 
specified by the command in question while FLUSH CACHE [EXT] operates on the 
whole cache -- so, it's not equivalent.

> Thanks.
> 
> /mjt

MBR, Sergei

  reply	other threads:[~2007-06-22 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 13:30 SATA: Is "DPO and FUA" ever supported? Michael Tokarev
2007-06-22 14:15 ` Sergei Shtylyov [this message]
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=467BD96C.4090005@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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).