linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: bytes/CDB of SCSI pass thru grossly limited maybe
Date: Mon, 23 Aug 2004 17:46:49 +0200	[thread overview]
Message-ID: <20040823154648.GB2301@suse.de> (raw)
In-Reply-To: <1092678938.4235.37.camel@patlinux.iomegacorp.com>

On Mon, Aug 16 2004, Pat LaVarre wrote:
> Jens A:
> 
> > in short, please try again :-)
> 
> I much appreciate your patient encouragement.  I now know I can ask:
> 
> Is there an ide-cd option to allow more bytes/CDB?
> 
> That is, an option analogous to the /sys/block/sr*/device/max_sectors
> setting of usb-storage, allowing up to the xFF:FF LBA's/CDB standard at
> t10.org?  Else can I help create such an option?
> 
> I see ioctl SG_IO chokes via EIO if bytes/CDB goes much above zero.
> 
> I ask for a workaround because a friend of mine cares.
> 
> I see EIO at 130 KiB/CDB, though happy at 128 KiB/CDB, when I try
> ide-cd.  I see usb-storage defaults to choke thruput off at 120 KiB/CDB,
> but thru /sys lets us reach a little farther above zero i.e. 512
> KiB/CDB.
> 
> How coordinated is our 2.6 effort to choke off thruput near zero across
> PATAPI, USB, FireWire, SPI, SATAPI, etc.?
> 
> Is there an ide-cd option to allow more bytes/CDB?

Ok, makes more sense to me now. The reason why I get confused is that I
don't consider the cdb more than the actual 10-16 bytes of command data
bytes, not the full structure of it.

But yes, different devices will have different max transfer values. As
I'm sure you know, ATAPI cannot do more than 128KiB per command. And
that is what q->max_sectors is set to, if you try and submit more than
this through SG_IO, bio_add_user() will complain and command will be
failed as you experienced.

max_sectors should be fully exposed so you don't have to guess.

-- 
Jens Axboe


  parent reply	other threads:[~2004-08-23 15:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 23:04 bytes/CDB of SCSI pass thru grossly limited maybe Pat LaVarre
2004-07-31 14:12 ` Jens Axboe
2004-08-16 17:55   ` Pat LaVarre
2004-08-17 18:07     ` Pat LaVarre
2004-08-23 15:46     ` Jens Axboe [this message]
2004-08-23 16:05       ` Pat LaVarre
2004-08-23 17:08         ` Jens Axboe
2004-08-23 17:28           ` Pat LaVarre
2004-08-23 18:17             ` Jens Axboe
2004-08-26 23:20               ` Pat LaVarre
2004-08-23 16:06       ` Jeff Garzik
2004-08-23 17:05         ` Pat LaVarre
2004-08-23 18:48         ` Luben Tuikov
2004-08-23 19:06           ` Jeff Garzik
2004-08-23 19:14             ` Luben Tuikov
     [not found] <A8E06BE4-F7BA-11D8-AC6B-00039398BB5E@ieee.org>
     [not found] ` <Pine.LNX.4.44L0 .0408271100590.1238-100000@ida.rowland.org>
2004-08-27 15:09 ` Alan Stern
2004-08-28 14:31   ` Jens Axboe
2004-08-28 15:14     ` Alan Stern
2004-08-28 15:36       ` Jens Axboe
2004-08-28 17:51     ` James Bottomley
2004-08-28 17:55       ` Jens Axboe
2004-08-28 18:20         ` James Bottomley
2004-08-28 18:41           ` Jens Axboe
2004-08-29 13:34             ` James Bottomley
2004-08-29 13:45               ` Jens Axboe
2004-08-30 18:15                 ` Pat LaVarre
2004-09-01 15:20                   ` Pat LaVarre

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=20040823154648.GB2301@suse.de \
    --to=axboe@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=p.lavarre@ieee.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;
as well as URLs for NNTP newsgroup(s).