From: Luben Tuikov <luben_tuikov@adaptec.com>
To: brking@us.ibm.com
Cc: Jeff Garzik <jgarzik@pobox.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/2] libata: support SATA devices on SAS HBAs
Date: Tue, 25 Oct 2005 09:40:33 -0400 [thread overview]
Message-ID: <435E35D1.4070907@adaptec.com> (raw)
In-Reply-To: <435E357D.1020800@us.ibm.com>
On 10/25/05 09:39, Brian King wrote:
> Luben Tuikov wrote:
>
>>On 10/24/05 18:17, Brian King wrote:
>>
>>
>>>The following patches enhance libata to allow SAS device drivers
>>>to utilize libata to talk to SATA devices. It introduces some
>>>new APIs which allow libata to be used without allocating a
>>>virtual scsi host. In the context of SAS, a struct ata_port
>>>is not a physical port, but rather becomes a virtual construct.
>>>
>>>Since my last post, I have removed the dependence on the host_set
>>>struct. The following two patches depend on the qc_transport patch:
>>>
>>>http://marc.theaimsgroup.com/?l=linux-ide&m=112845939215286&w=2
>>>
>>>The API is the same as the last time I posted it to linux-ide,
>>>but here is the description again:
>>>
>>>New APIs:
>>>
>>>ata_sas_port_alloc - Allocate an ata_port
>>>ata_sas_port_init - Initialize an ata_port (probe device, etc)
>>>ata_sas_port_destroy - Free an ata_port allocated by ata_sas_port_alloc
>>>ata_sas_slave_configure - configure scsi device
>>>ata_sas_queuecmd - queue a scsi command, similar to ata_scsi_queuecomand
>>>
>>>These new APIs can be used either directly by a SAS LLDD or could be used
>>>by the SAS transport class.
>>>
>>>Possible usage for a SAS LLDD would be:
>>>
>>>scsi_scan_host
>>> slave_alloc
>>> ata_sas_port_alloc
>>> ata_sas_port_init
>>> slave_configure
>>> ata_sas_slave_configure
>>>
>>>Commands received by the LLDD for SATA devices would call ata_sas_queuecmd.
>>>
>>>Device teardown would occur with:
>>>
>>>slave_destroy
>>> ata_sas_port_destroy
>>
>>
>>Hey Brian,
>>
>>That's admireable effort. Is there a git tree I can pull from which has
>>these patches? (I don't mind using the patches themselves as well.)
>>
>>I'll take a look indepth and comment further.
>>
>>Thanks,
>> Luben
>
>
> Hey Luben,
>
> I don't have a git tree setup, just the three patches.
I assume you've tested them already on the SAS Transport Layer?
Luben
--
http://linux.adaptec.com/sas/
http://www.adaptec.com/sas/
next prev parent reply other threads:[~2005-10-25 13:40 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
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 [this message]
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=435E35D1.4070907@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=brking@us.ibm.com \
--cc=bzolnier@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 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.