public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Douglas Gilbert <dougg@torque.net>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	bunk@fs.tum.de
Subject: Re: Is scsi_cmnd::underflow still useful?
Date: Mon, 12 Jul 2004 22:09:20 -0700	[thread overview]
Message-ID: <20040713050920.GA31062@one-eyed-alien.net> (raw)
In-Reply-To: <1089680114.2074.198.camel@mulgrave>

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

On Mon, Jul 12, 2004 at 07:55:13PM -0500, James Bottomley wrote:
> On Mon, 2004-07-12 at 14:40, Douglas Gilbert wrote:
> > Doesn't look like many LLDs act on scsi_cmnd::underflow.
> > Seems to me that scsi_cmnd::resid is a more general
> > replacement.
> 
> well, I know I suggested a recent use of it to the USB people , so I
> don't think it's entirely unused.  resid can't be a replacement because
> they mean different things:
> 
> resid - number of bytes left over after a transaction
> underflow - driver must return error if less than this amount
> transferred.

I think the recent USB usage of it was because some mid-level drivers look
for the error condition related to the underflow value.

We don't really use it, other than to trigger an error.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

Stef, you just got beaten by a ball of DIRT.
					-- Greg
User Friendly, 12/7/1997

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-07-13  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 19:40 Is scsi_cmnd::underflow still useful? Douglas Gilbert
2004-07-13  0:55 ` James Bottomley
2004-07-13  5:09   ` Matthew Dharm [this message]
2004-07-13 22:09   ` Douglas Gilbert

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=20040713050920.GA31062@one-eyed-alien.net \
    --to=mdharm-scsi@one-eyed-alien.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bunk@fs.tum.de \
    --cc=dougg@torque.net \
    --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