From: Luben Tuikov <tluben@rogers.com>
To: dougg@torque.net
Cc: Jens Axboe <axboe@suse.de>, Jeff Garzik <jgarzik@pobox.com>,
linux-scsi@vger.kernel.org
Subject: Re: "do ata" scsi command?
Date: Sat, 17 May 2003 03:49:24 -0400 [thread overview]
Message-ID: <3EC5E984.90408@rogers.com> (raw)
In-Reply-To: <3EC5B7DE.4060402@torque.net>
> In SAS we have a pure SCSI command set protocol (SSP),
Those are not command set protocols, they are _transport_
protocols (specific to the SAS interconnect). (Command Set
Protocols are things like SBC, RBC, MMC, etc, i.e. ``above''
SAM-3/SPC-3.)
> a management protocol (SMP) and a protocol for tunnelling
> the ATA/PI command set/task file over an SAS link (STP)**.
> The idea is that users will be able to plug either SAS
> or SATA disks into their RAID backplanes.
>
> So we are likely to get a SAS HBA in the SCSI subsystem
> (from Justin??) that is an initiator for those three
> protocols. How do we handle STP??
STP talks to the ATA application layer (IDE layer).
Its only (business-political) purpose is to allow SATA
over the SAS interconnect.
Overall, that'd be one complicated LLDD if it supported all three...
--
Luben
next prev parent reply other threads:[~2003-05-17 7:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 23:02 "do ata" scsi command? Jeff Garzik
2003-05-16 6:03 ` Jens Axboe
2003-05-16 15:54 ` Jeff Garzik
2003-05-16 16:05 ` Jens Axboe
2003-05-16 16:30 ` Jeff Garzik
2003-05-16 16:35 ` Jens Axboe
2003-05-16 16:41 ` Jeff Garzik
2003-05-16 16:43 ` Jens Axboe
2003-05-16 16:46 ` Jeff Garzik
2003-05-17 4:17 ` Douglas Gilbert
2003-05-17 7:49 ` Luben Tuikov [this message]
2003-05-16 16:35 ` Jeff Garzik
2003-05-16 16:40 ` Jens Axboe
2003-05-16 16:45 ` Jeff Garzik
2003-05-16 18:37 ` Andries Brouwer
2003-05-16 19:02 ` Luben Tuikov
2003-05-16 18:50 ` Luben Tuikov
2003-05-16 19:31 ` 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=3EC5E984.90408@rogers.com \
--to=tluben@rogers.com \
--cc=axboe@suse.de \
--cc=dougg@torque.net \
--cc=jgarzik@pobox.com \
--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