From: Douglas Gilbert <dougg@torque.net>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Jens Axboe <axboe@suse.de>,
Linux-ide <linux-ide@vger.kernel.org>
Subject: Re: libata transfer mode & FUA & mode sense page
Date: Fri, 18 Nov 2005 10:33:57 +1000 [thread overview]
Message-ID: <437D2175.5050600@torque.net> (raw)
In-Reply-To: <437B649C.5080708@gmail.com>
Tejun Heo wrote:
> Hello, Jeff, Douglas and Jens.
>
> I've been trying to port the ordered reimplementation patchset over to
> post-2.6.15 head of blk tree. This tree now contains PIO and mode sense
> improvements for libata.
>
> ATA FUA is interesting in that it's supported only for multisector PIO
> and DMA protocols. There is no ATA_CMD_PIO_WRITE_FUA_EXT. So, when
> generating mode sense page, the status of FUA supported bit is dependent
> on the configured transfer mode. As there doesn't seem to be dynamic
> transfer mode configuration yet, I'm thinking of simply passing ap or
> device down to mode sense functions and use it to report FUA status. How
> does that sound?
>
> If dynamic transport configuration is implemented in the future (from EH
> or explicit user input), this FUA bit will go on and off depending on
> transfer mode. Ugh... It seems that we'll need a way to raise UA for
> configuration change and trigger revalidation of SCSI disk device.
Tejun,
The DPOFUA bit in the mode sense response header only
indicates capability and cannot be changed via a
MODE SELECT command. Individual READ and WRITE SCSI
commands (other than the 6 byte variants) have individual
FUA and DPO (disable page out) bits. Further, I have
asked for clarification as SBC and SAT say the the
DPOFUA bit implies that both the DPO _and_ FUA bits
are supported but the DPO bit is unspecified in sat-r07.
If the DPOFUA bit changes "on the fly" then a UA with
asc/ascq=0x3f/0x0 ["Target operating conditions have
changed"] may be appropriate (or 0x3f/0x2). The linux
scsi mid level (and sd driver) treat UAs as a nuisance
but this may need to change.
It seems that asynchronous notifications at the command
level are being deprecated across all t10 command sets
in favour of REQUEST SENSE polling and/or deferred
errors. There are still asynchronous notifications
around (SAS just added a few) but they are being
relegated to the transport level.
Doug Gilbert
next prev parent reply other threads:[~2005-11-18 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 16:55 libata transfer mode & FUA & mode sense page Tejun Heo
2005-11-16 17:15 ` Jeff Garzik
2005-11-18 0:33 ` Douglas Gilbert [this message]
2005-11-23 8:25 ` Tejun
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=437D2175.5050600@torque.net \
--to=dougg@torque.net \
--cc=axboe@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--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).