From: James Bottomley <James.Bottomley@steeleye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Markus Lidel <Markus.Lidel@shadowconnect.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: I2O enhancement for Adaptec management software
Date: 07 Apr 2004 16:10:01 -0500 [thread overview]
Message-ID: <1081370204.1747.5.camel@mulgrave> (raw)
In-Reply-To: <20040405111245.A4077@infradead.org>
On Mon, 2004-04-05 at 05:12, Christoph Hellwig wrote:
> SG_IO is for scsi passthrough. now you could invent fake scsi command
> opcodes for native messages, but at that point it starts to get silly.
Actually, no it's not. SG_IO will to IDE taskfile passthrough just as
well. As arjan says, it's for native command passthrough.
Now, since the dpt_i20 commontly accepts SCSI commands it would have to
have some way to distinguish these "native" commands from other SCSI
commands, but surely a vendor specific service action would do that.
The consummate advantage is that we don't have to have the driver trying
to construct the SG list on its own (which is what about 50% of this
patch is doing), it can use the block layer to do that on a passed in
area of application memory.
James
next prev parent reply other threads:[~2004-04-07 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 9:43 I2O enhancement for Adaptec management software Markus Lidel
2004-04-05 10:02 ` Arjan van de Ven
2004-04-05 10:05 ` Christoph Hellwig
2004-04-05 10:10 ` Arjan van de Ven
2004-04-05 10:12 ` Christoph Hellwig
2004-04-07 21:10 ` James Bottomley [this message]
2004-04-08 9:27 ` Markus Lidel
2004-04-08 12:29 ` James Bottomley
2004-04-08 13:14 ` Markus Lidel
2004-04-23 8:31 ` Markus Lidel
2004-04-05 10:18 ` Christoph Hellwig
2004-04-05 10:37 ` Markus Lidel
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=1081370204.1747.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Markus.Lidel@shadowconnect.com \
--cc=arjanv@redhat.com \
--cc=hch@infradead.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