public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
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 09:43:27 -0600	[thread overview]
Message-ID: <45EAE91F.5070206@cs.wisc.edu> (raw)
In-Reply-To: <1173018667.3372.36.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Sun, 2007-03-04 at 00:36 -0700, Dachepalli, Sudhir wrote:
>> Our driver gets called in with the following fashion through the
>> queuecommand.
>>
>> scsi_request_fn() -> scsi_dispatch_cmd() -> rtn =
>> host->hostt->queuecommand(cmd, scsi_done);
>>
>> We are using the "cmd" ( scsi_cmnd) as a pass through with out touching
>> the "request_buffer" and "request_bufflen".
>>
>> We do not allocate memory similar to sg or st for page allocations.
>>
>> The request_buffer should already contain the scatter gather list built.
> 
> We're trying not to wrapper pass throughs in SCSI commands (unless
> defined by standard like the ATA ones).  However, I'm not entirely sure
> what you're trying to do ... can you post a link to the driver so that
> we can see if there's a better way?
> 

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

  reply	other threads:[~2007-03-04 15:44 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 [this message]
2007-03-04 15:57                         ` James Bottomley
2007-03-04 16:21                           ` Mike Christie
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=45EAE91F.5070206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox