All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Liran Schour <LIRANS@il.ibm.com>
Cc: Douglas Gilbert <dougg@torque.net>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	linux-scsi-owner@vger.kernel.org
Subject: Re: SCSI commands order when using scsi_do_req
Date: Mon, 06 Jun 2005 09:32:53 -0500	[thread overview]
Message-ID: <1118068373.5045.25.camel@mulgrave> (raw)
In-Reply-To: <OFDF05D602.08E5F1FA-ONC2257018.002E3CA5-C2257018.002EF1DD@il.ibm.com>

On Mon, 2005-06-06 at 11:32 +0300, Liran Schour wrote:
> In order to run our OSD SCSI initiator on top of the Linux SCSI layer
> we have needed to do the following changes to the SCSI code:
> 1. Redefine MAX_COMMAND_SIZE to 256 byte.

There's more than just you interested in this one, so separating this
feature out from all the rest would be helpful.

> 2. Define a new scatter gather structures that includes two virtual buffers
>    on for data out and one for data in. (implementing bidirectional
> commands)
>    The SCSI middle layer doesn't now this new structure (only ULD and LLD).

Yes, this is the nasty one ... and why OSD hasn't been incredibly
popular; bidirectional commands necessitate fairly sweeping changes to
all LLDs to support.  However, I don't see how we can get away without
the mid-layer knowing, since it's the entity that constructs the sglists
and the sglists have to be separated between the in and out pieces.

> 3. The problem above - define a new scsi_do_req that inserts our commands
> to
>    the tail of the Q.

Well, the solution, I think, is going to be the block execute one, which
will allow head or tail insertion.

James



  reply	other threads:[~2005-06-06 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 17:31 SCSI commands order when using scsi_do_req Liran Schour
2005-06-02 17:54 ` James Bottomley
2005-06-03  0:03   ` Douglas Gilbert
2005-06-06  8:32     ` Liran Schour
2005-06-06 14:32       ` James Bottomley [this message]
2005-06-07  9:27         ` Liran Schour
2005-06-17  9:08   ` Vladislav Bolkhovitin

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