From: Ric Wheeler <rwheeler@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: USB storage & write barrier support?
Date: Mon, 23 Nov 2009 15:57:48 -0500 [thread overview]
Message-ID: <4B0AF74C.6070600@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911231544550.2958-100000@iolanthe.rowland.org>
On 11/23/2009 03:49 PM, Alan Stern wrote:
> On Mon, 23 Nov 2009, Ric Wheeler wrote:
>
>> What we need is to pass down cache flush commands (ATA_CACHE_FLUSH_EXT is what
>> flushed the cache for ATA/S-ATA devices). Even with a command-queue length of 1,
>> the write cache a USB connected s-ata drive would still loose data on power off
>> without this kind of support.
>
> You can't send ATA commands directly over a USB connection without
> using a passthru protocol of some sort. Some of the USB interfaces in
> various drive enclosures support such a protocol but a lot of them
> don't.
>
> Of course, you _can_ send SCSI's SYNCHRONIZE CACHE command. What
> ATA/SATA command (if any) the drive's USB interface will translate it
> into is known only to the interface's manufacturer. Nevertheless,
> that's what we've been depending on because that's what the sd driver
> uses.
>
> Alan
>
That makes sense - so the usb storage stack does the right thing, what happens
is up to the SCSI -> ATA translation in the target device.
If I still had occasional access to analyzers, we could always test & verify
that some of the common enclosures work correctly but I have unfortunately lost
my toys :-)
Thanks!
Ric
prev parent reply other threads:[~2009-11-23 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 20:12 USB storage & write barrier support? Ric Wheeler
2009-11-23 20:37 ` Alan Stern
2009-11-23 20:46 ` Ric Wheeler
2009-11-23 20:49 ` Alan Stern
2009-11-23 20:57 ` Ric Wheeler [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=4B0AF74C.6070600@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.