public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Arjan van de Ven <arjanv@redhat.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: I2O enhancement for Adaptec management software
Date: Thu, 08 Apr 2004 11:27:52 +0200	[thread overview]
Message-ID: <40751B18.9040403@shadowconnect.com> (raw)
In-Reply-To: <1081370204.1747.5.camel@mulgrave>

Hello,

James Bottomley 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 patch is for i2o_config, not for dpt_i2o! These are different 
drivers and have (from the architecture view) not much in common. 
dpt_i2o is a driver which let access to the disks entirely using the 
SCSI subsystem. The i2o subsystem uses i2o_core and i2o_block to access 
disks (which doesn't use SCSI at all), and also have an SCSI driver, 
which let access to each connected disk (i2o_scsi). But the i2o_scsi is 
not needed for normal disk access.

It's very funny, that i copied the patch 1:1 from dpt_i2o, where it is 
used too, and nobody ever complained about it :-D But don't understand 
me wrong, if there is a better way to do it, i'll try to do it this way.

> 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.

Than i have to move the patch to the i2o_scsi driver, because the 
i2o_scsi uses the SCSI subsystem already. But IMHO the i2o_config driver 
is better suited, cause the patch is only needed for the management 
software. One last question, could i use the SG list building function 
without using the SCSI layer?

Thank you very much.



Best regards,


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com

  reply	other threads:[~2004-04-08  9:26 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
2004-04-08  9:27           ` Markus Lidel [this message]
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=40751B18.9040403@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=James.Bottomley@steeleye.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