From: Douglas Gilbert <dougg@torque.net>
To: Luben Tuikov <luben@splentec.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: sense buffer length for REQUEST SENSE?
Date: Sat, 27 Jul 2002 00:47:17 -0400 [thread overview]
Message-ID: <3D4225D5.9A8ED692@torque.net> (raw)
In-Reply-To: 3D420D77.A4633D9C@splentec.com
Luben Tuikov wrote:
>
> The sense buffer size is 64 bytes.
I can plead guilty to that. A finger in the air trade off
between the standard ** and reality. It previously was 16
bytes (changed in lk 2.3 I think). At 64 bytes it matches
the size of the Scsi_Cmnd::sense_buffer array
(and Scsi_Request::sr_sense_buffer).
> According to SAM-3, to make sure that that an application
SAM-3 is new (it branched off recently from SAM-2) and adds
SAS to its protocol tables. SAS is SCSI over Serial ATA
type infrastructure ... SAS may displace Ultra 640.
> client has gotten all the sense data the sense buffer
> should be 252 bytes.
Yes I can see that number in SPC-3. Has anyone every seen
an actual REQUEST SENSE response (sense buffer) anywhere near
that size? The new "descriptor" sense data format should
further reduce the size requirement.
> How safe am I to actually set the allocation length
> to 252 bytes? (in terms of borken hardware devices, etc.)
Following the lead from 36 byte INQUIRYs, what does Windows
do?
BTW I have not seen a report of the current 64 byte allocation
length causing a problem.
** SCSI-2 said 18 bytes or greater and now SPC-3 says at least
252 bytes.
Doug Gilbert
next prev parent reply other threads:[~2002-07-27 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 3:03 sense buffer length for REQUEST SENSE? Luben Tuikov
2002-07-27 4:47 ` Douglas Gilbert [this message]
2002-07-27 3:57 ` Matthew Jacob
2002-07-27 8:50 ` Steve McIntyre
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=3D4225D5.9A8ED692@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=luben@splentec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.