From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org, htejun@gmail.com
Subject: [PATCH 0/2] libata: MODE SELECT
Date: Sun, 23 Oct 2005 16:23:03 +1000 [thread overview]
Message-ID: <435B2C47.8070708@torque.net> (raw)
Jeff,
Here is another shot at adding MODE SELECT to
libata. I have used sat-r06, sbc-3 and spc-4 as
a guide. Compliance on the ATA side has some issues:
- no mechanism to issue 2 or more ATA commands
when translating a single SCSI command [in the
upstream branch, there have been patches ...]
- relies on the dev->id array (IDENTIFY DEVICE response)
always being up to date. Despite assurances I cannot
see how that is the case when multiple hosts
(initiators) can access a SATA disk.
This patch is broken into two parts and is against
libata-dev's upstream branch:
1) strengthen MODE SENSE processing and make
default mode pages visible within libata-scsi.c
2) add MODE SELECT SCSI command support.
Two attributes can be changed with these patches:
- WCE: write cache enable [cache mode page]
- DRA: disable read ahead [cache mode page]
Testing: upstream branch seems to be broken wrt SG_IO
as the largest amount of data that can be sent per
command is 4 KB. A 50 MB write (segmented to 4 KB per
command) slowed down from 14 seconds with WCE=1 to
107 seconds with WCE=0. sg_dd was used for the transfer
and sdparm to change WCE. ST380013AS disk and
sata_sil LLD.
The attachments are mime text because I wasn't able
to do otherwise.
Signed-off-by: Douglas Gilbert <dougg@torque.net>
Doug Gilbert
next reply other threads:[~2005-10-23 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 6:23 Douglas Gilbert [this message]
2005-10-28 19:59 ` [PATCH 0/2] libata: MODE SELECT Jeff Garzik
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=435B2C47.8070708@torque.net \
--to=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).