From: Mike Christie <michaelc@cs.wisc.edu>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Dachepalli, Sudhir" <Sudhir.Dachepalli@lsi.com>,
Benny Halevy <bhalevy@panasas.com>,
Jens Axboe <jens.axboe@oracle.com>,
Boaz Harrosh <bharrosh@panasas.com>,
linux-scsi@vger.kernel.org
Subject: Re: Possible bug in scsi_lib.c:scsi_req_map_sg()
Date: Sun, 04 Mar 2007 10:21:11 -0600 [thread overview]
Message-ID: <45EAF1F7.9040102@cs.wisc.edu> (raw)
In-Reply-To: <1173023824.3372.53.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Sun, 2007-03-04 at 09:43 -0600, Mike Christie wrote:
>> There are trying to do a scsi level multipath driver for RDAC support.
>> And they are trying to do something similar to request based multipath
>> (route requests instead of bios but in their case they are routing
>> scsi_cmnds instead of requests).
>
> I guessed it might be something like that ...
>
> The SCSI driver layer wasn't designed to stack like that ... hence the
> problems of setup and teardown of the sg list. Wouldn't it just be
> easier to make request based multi-path work? Unfortunately, you can't
> avoid the request system because what you want to do is resubmit an I/O
> without having the mid-layer execute the prepare function (which is
> where it's mapped) so you need the REQ_DONTPREP flag.
>
I think they get around this and other request settings that need
resetting by using scsi_execute_async. They will take the command, data
direction and buffer fields from the original scsi_cmnd, then pass those
on to scsi_ececute_async which would allocate a new request and then as
you know that new request gets sent to the scsi layer and looks like a
brand new request. So I misspoke above. It might be better to say they
are using it for routing what the other multipath layers would call
cloned commands.
next prev parent reply other threads:[~2007-03-04 16:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 17:44 Possible bug in scsi_lib.c:scsi_req_map_sg() Boaz Harrosh
2006-11-27 19:13 ` Mike Christie
2006-11-27 19:27 ` Mike Christie
2006-11-27 21:52 ` Kai Makisara
2006-11-28 18:57 ` Jens Axboe
2006-11-29 9:30 ` Benny Halevy
2007-03-02 16:45 ` Dachepalli, Sudhir
2007-03-02 21:19 ` Mike Christie
2007-03-02 21:59 ` Mike Christie
2007-03-02 23:45 ` Dachepalli, Sudhir
2007-03-04 0:04 ` Mike Christie
2007-03-04 7:36 ` Dachepalli, Sudhir
2007-03-04 14:31 ` James Bottomley
2007-03-04 15:43 ` Mike Christie
2007-03-04 15:57 ` James Bottomley
2007-03-04 16:21 ` Mike Christie [this message]
2007-03-04 16:51 ` James Bottomley
2007-03-04 17:04 ` Mike Christie
2007-03-04 17:07 ` Mike Christie
2007-03-04 18:00 ` Dachepalli, Sudhir
2007-03-04 18:14 ` James Bottomley
2007-03-04 19:06 ` Dachepalli, Sudhir
2007-03-05 13:00 ` Christoph Hellwig
2007-03-05 13:02 ` Christoph Hellwig
2006-11-27 23:33 ` James Bottomley
2006-11-28 15:44 ` Boaz Harrosh
2006-11-28 17:30 ` Mike Christie
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=45EAF1F7.9040102@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=Sudhir.Dachepalli@lsi.com \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=jens.axboe@oracle.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 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.