From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>,
Douglas Gilbert <dougg@torque.net>, Jens Axboe <axboe@suse.de>
Cc: Linux-ide <linux-ide@vger.kernel.org>
Subject: libata transfer mode & FUA & mode sense page
Date: Thu, 17 Nov 2005 01:55:56 +0900 [thread overview]
Message-ID: <437B649C.5080708@gmail.com> (raw)
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
next reply other threads:[~2005-11-16 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 16:55 Tejun Heo [this message]
2005-11-16 17:15 ` libata transfer mode & FUA & mode sense page Jeff Garzik
2005-11-18 0:33 ` Douglas Gilbert
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=437B649C.5080708@gmail.com \
--to=htejun@gmail.com \
--cc=axboe@suse.de \
--cc=dougg@torque.net \
--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).