public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@classic.engr.sgi.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: request_buffer versus buffer in Scsi_Cmnd
Date: Fri, 27 Sep 2002 18:50:59 -0700 (PDT)	[thread overview]
Message-ID: <10209271850.ZM105071@classic.engr.sgi.com> (raw)
In-Reply-To: Mike Anderson <andmike@us.ibm.com> "Re: request_buffer versus buffer in Scsi_Cmnd" (Sep 27,  9:29am)

On Sep 27,  9:29am, Mike Anderson wrote:
> 
> Jeremy Higdon [jeremy@classic.engr.sgi.com] wrote:
> > I notice that the qlogicfc driver calls pci_map_sg with the request_buffer
> > field and pci_unmap_sg with the buffer field.
> > 
> > >From looking at the code in drivers/scsi/scsi*, it would appear that they
> > are mostly the same, and the fact that qlogicfc works would seem to confirm
> > that.  However, the fact that there are two different fields leads me
> > to ask what the difference is supposed to be.
> > 
> 
> There are a few fields in the Scsi_Cmnd that are duplicated to contain
> the original values that the scsi cmd was submitted with mostly for retry.
> 
> Some Pairs:
> 	request_buffer, buffer
> 	request_bufflen, bufflen
> 	use_sg, old_use_sg
> 	etc.
> 
> a few more are listed in the scsi_retry_command.
> 
> -andmike
> --
> Michael Anderson
> andmike@us.ibm.com
> 
>-- End of excerpt from Mike Anderson

Okay, thanks.  It sounds as though we should never use the buffer field,
then.  It also sounds as though the qlogicfc code is a bug, but that
it won't bite unless buffer and request_buffer are different (would that
be for a Request Sense after check condition, which qlogicfc would
never need?).

jeremy

      reply	other threads:[~2002-09-28  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  9:15 request_buffer versus buffer in Scsi_Cmnd Jeremy Higdon
2002-09-27 16:29 ` Mike Anderson
2002-09-28  1:50   ` Jeremy Higdon [this message]

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=10209271850.ZM105071@classic.engr.sgi.com \
    --to=jeremy@classic.engr.sgi.com \
    --cc=andmike@us.ibm.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