From: James Bottomley <James.Bottomley@steeleye.com>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: dougg@torque.net, SCSI Mailing List <linux-scsi@vger.kernel.org>,
linux-scsi-owner@vger.kernel.org
Subject: Re: bidirectional, long commands + OSD
Date: 30 Jan 2004 09:25:34 -0500 [thread overview]
Message-ID: <1075472734.1999.25.camel@mulgrave> (raw)
In-Reply-To: <OF04DCDB82.2269D90E-ON42256E2B.003249AE-42256E2B.003A8576@il.ibm.com>
On Fri, 2004-01-30 at 05:39, Liran Schour wrote:
> Most of the HBAs today can't support execution of OSD SCSI commands due to
> the
> extended CDB's length and the bidirectional data movement. But when OSD
> technology
> will catch a momentum we will see more and more vendors that will support
> this features.
> My point is that maybe we can keep the current interface while expanding it
> to support
> the needed features by the SCSI OSD commands.
Actually, I'm sure they can. Most HBA's operate using a scripted
firmware interface (like the LSI scripts or the Adaptec sequencer). As
long as the scripts are updated, it's no trouble to support multiple
data pointers and large CDBs (even the 53c700, a 1990s era chip can do
this). I also know seagate is working on an actual single disc that
supports OSD, so I expect even the closed firmware chip sets will
eventually be updated.
> I have used only ISCSI and TCP/IP (non SCSI) OSD devices. In the devices
> that
> I have used the transitions of data where isolated - first DATA OUT then
> DATA IN.
> But an OSD device can do the following data transitions: DATA IN (user
> data) ; DATA OUT
> (set attributes data and get attributes list) ; DATA IN (retrieved
> attributes data).
Yes, that's what I feared. The spec implies this as well. Behaviour
like that requires two data pointers.
James
next prev parent reply other threads:[~2004-01-30 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1075396141.2381.65.camel@mulgrave>
2004-01-30 10:39 ` bidirectional, long commands + OSD Liran Schour
2004-01-30 14:25 ` James Bottomley [this message]
2004-01-26 17:01 [PATCH] 2.6.2-rc2 - MPT Fusion driver 3.00.02 update Moore, Eric Dean
2004-01-26 17:05 ` James Bottomley
2004-01-27 8:48 ` Douglas Gilbert
2004-01-28 20:08 ` James Bottomley
2004-01-29 13:07 ` bidirectional, long commands + OSD Douglas Gilbert
2004-01-29 22:37 ` Liran Schour
2004-01-30 14:22 ` James Bottomley
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=1075472734.1999.25.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=LIRANS@il.ibm.com \
--cc=dougg@torque.net \
--cc=linux-scsi-owner@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