From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: dougg@torque.net, brking@us.ibm.com,
Luben Tuikov <luben_tuikov@adaptec.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
t.schorpp@gmx.de
Subject: Re: [PATCH 1/2] libata: Remove dependence on host_set->dev for SAS
Date: Thu, 01 Dec 2005 21:05:44 -0500 [thread overview]
Message-ID: <438FABF8.3020802@pobox.com> (raw)
In-Reply-To: <58cb370e0511240012r64ad150eo90553b230992424e@mail.gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> On 11/24/05, Jeff Garzik <jgarzik@pobox.com> wrote:
>
>>Douglas Gilbert wrote:
>>
>>>I don't think a SATL is that easy. One SCSI command can
>>>translate into zero or more ATA commands. If it translates
>>>to multiple commands, then there is the possibility of an
>>>error prior to the last in the sequence of ATA commands
>>>(how to report; rollback needed ?). The SATL needs to hold
>>>state and needs a service thread if it is to support the
>>>IMMED bit on some commands (e.g. START STOP UNIT).
>>
>>It needs a conceptual service thread, not necessarily an explicit one.
>>
>>With REQUEST SENSE, I've demonstrated how to report errors with each
>>step in the sequence. With demo patches I've posted, I've demonstrated
>>(using qc->private_data) how to hold state.
>>
>>
>>
>>>libata still has a ways to go to catch up to SAT rev 7
>>>but has made some good progress lately with the addition
>>>of the ATA pass through commands (lk 2.6.15-rc1 and onward).
>>>smartmontools (just prior to 5.34) now works with '-d ata'
>>>on libata-connected SATA disks. The '-d ata' ** overrides
>>>the guess of a SCSI disk based on the device node (e.g.
>>>/dev/sda) and uses the HDIO_DRIVE_CMD and HDIO_DRIVE_TASK
>>>ioctls. The absence of support for the HDIO_DRIVE_TASKFILE
>>>ioctl means that "selective" self-test can't be done.
>>>I'm not sure if moving smartmontools to the ATA PASS THROUGH
>>>SCSI commands will win back the "selective" self-test
>>>capability. Anyway, going to those ATA PASS THROUGH SCSI
>>
>>ATA passthru can do anything the legacy IDE ioctls can do (and more).
>
>
> [ definitely ATA passthru is the way to go but... ]
>
> discrete taskfiles?
what is this?
> multi-PIO?
what is this? multi-sector PIO, such as READ MULTIPLE SECTORS? ATA
passthru can do that.
> setting transfer speed?
That's not a limitation of passthru, but a limitation of the driver. I
don't yet see the value...
Jeff
next prev parent reply other threads:[~2005-12-02 2:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 21:56 [RFC 0/2] libata: support SATA devices on SAS HBAs Brian King
2005-10-03 21:58 ` [RFC 1/2] libata: configurable host_set lock Brian King
2005-10-03 21:58 ` [RFC 2/2] libata: support SATA devices on SAS HBAs Brian King
2005-10-04 9:56 ` [RFC 0/2] " Jeff Garzik
2005-10-04 10:22 ` Bartlomiej Zolnierkiewicz
2005-10-04 20:56 ` Bartlomiej Zolnierkiewicz
2005-10-05 20:59 ` Jeff Garzik
2005-10-24 22:17 ` [PATCH " Brian King
2005-10-24 22:19 ` [PATCH 1/2] libata: Remove dependence on host_set->dev for SAS Brian King
2005-10-25 17:53 ` Jeff Garzik
2005-10-25 19:30 ` Brian King
2005-10-25 19:43 ` Jeff Garzik
2005-10-25 22:48 ` Luben Tuikov
2005-10-27 16:05 ` Brian King
2005-10-27 20:15 ` Luben Tuikov
2005-11-24 0:53 ` Douglas Gilbert
2005-11-24 1:07 ` Jeff Garzik
2005-11-24 8:12 ` Bartlomiej Zolnierkiewicz
2005-12-02 2:05 ` Jeff Garzik [this message]
2005-12-02 8:07 ` Bartlomiej Zolnierkiewicz
2005-12-02 10:28 ` Douglas Gilbert
2005-12-02 10:48 ` Jeff Garzik
2005-11-29 22:13 ` Brian King
2005-10-24 22:20 ` [PATCH 2/2] libata: Add support for SATA attachment to SAS adapters Brian King
2005-10-25 17:58 ` Jeff Garzik
2005-10-25 12:59 ` [PATCH 0/2] libata: support SATA devices on SAS HBAs Luben Tuikov
2005-10-25 13:39 ` Brian King
2005-10-25 13:40 ` Luben Tuikov
2005-10-25 13:53 ` Brian King
2005-10-25 14:08 ` Luben Tuikov
2005-10-25 14:27 ` Brian King
2005-10-25 17:51 ` Jeff Garzik
2005-10-25 17:57 ` [RFC " Brian King
2005-10-25 18:07 ` 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=438FABF8.3020802@pobox.com \
--to=jgarzik@pobox.com \
--cc=brking@us.ibm.com \
--cc=bzolnier@gmail.com \
--cc=dougg@torque.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=t.schorpp@gmx.de \
/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).