From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Brian King <brking@us.ibm.com>,
James.Bottomley@steeleye.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: Add scsi_device max_cmd_len
Date: Sat, 01 Apr 2006 12:31:15 +0200 [thread overview]
Message-ID: <442E5673.30808@s5r6.in-berlin.de> (raw)
In-Reply-To: <442B15F4.30506@pobox.com>
Jeff Garzik wrote on 2006-03-30:
> James Bottomley wrote:
>> This really doesn't look correct. What you want is a sata transport
>> class with a max command length in the host device.
>
> Christoph Hellwig wrote:
>> this sounds wrong to me. cdb length is a limitation of the host
>> (driver).
>> A target will reject unknown commands, no matter what length they have.
>
> In practice, CDB length may be limited by both the host and the device.
> This applies to ATAPI, and some USB storage too IIRC. For ATAPI, you
> read the CDB length from the device's IDENTIFY PACKET DEVICE info page.
BTW, in case of SBP-2 devices, the CDB length is a property of the
logical unit and is read from the IEEE 1394 node's configuration ROM.
Linux' sbp2 driver implements only a CDB length of 12 bytes though.
--
Stefan Richter
-=====-=-==- -=-- ----=
http://arcgraph.de/sr/
prev parent reply other threads:[~2006-04-01 10:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 22:17 [PATCH 1/2] scsi: Add scsi_device max_cmd_len Brian King
2006-03-28 22:29 ` James Bottomley
2006-03-28 22:38 ` Brian King
2006-03-28 22:49 ` James Bottomley
2006-03-29 0:03 ` Brian King
2006-03-29 0:12 ` James Bottomley
2006-03-29 4:42 ` Brian King
2006-03-29 23:22 ` Jeff Garzik
2006-03-29 9:11 ` Christoph Hellwig
2006-03-29 14:15 ` Brian King
2006-03-29 15:05 ` Christoph Hellwig
2006-03-29 23:19 ` Jeff Garzik
2006-03-30 16:39 ` Brian King
2006-03-30 16:42 ` Brian King
2006-04-04 9:25 ` Jeff Garzik
2006-04-07 13:36 ` Brian King
2006-04-01 10:31 ` Stefan Richter [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=442E5673.30808@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@steeleye.com \
--cc=brking@us.ibm.com \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).