From: Douglas Gilbert <dougg@torque.net>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: Steve Byan <smb@egenera.com>, Bryan Henderson <hbryan@us.ibm.com>,
linux-scsi@vger.kernel.org
Subject: Re: SCSI target and IO-throttling
Date: Tue, 14 Mar 2006 15:54:32 -0500 [thread overview]
Message-ID: <44172D88.6070201@torque.net> (raw)
In-Reply-To: <4411C99C.9040200@vlnb.net>
Vladislav Bolkhovitin wrote:
> Steve Byan wrote:
<snip>
> BTW, do you have any statistic how many modern SCSI disks support those
> features (ORDERED, ACA, UA_INTLCK_CTL, etc)? Few years ago none of
> available for us SCSI hardware, including tape libraries, supported ACA.
> It was not very modern for that time, though
Vlad,
Here is part of the control mode page from a
recent SCSI disk (Cheetah 15k.4) :
# sdparm -p co /dev/sdb -ll
/dev/sdb: SEAGATE ST336754SS 0003
Direct access device specific parameters: WP=0 DPOFUA=1
Control mode page [PS=1]:
TST 0 [cha: n, def: 0, sav: 0] Task set type
0: lu maintains one task set for all I_T nexuses
1: lu maintains separate task sets for each I_T nexus
TMF_ONLY 0 [cha: n, def: 0, sav: 0] Task management functions only
D_SENSE 0 [cha: n, def: 0, sav: 0] Descriptor format sense data
GLTSD 0 [cha: y, def: 1, sav: 0] Global logging target save disable
RLEC 0 [cha: y, def: 0, sav: 0] Report log exception condition
QAM 0 [cha: y, def: 0, sav: 0] Queue algorithm modifier
0: restricted re-ordering; 1: unrestricted
QERR 0 [cha: n, def: 0, sav: 0] Queue error management
0: only affected task gets CC; 1: affected tasks aborted
3: affected tasks aborted on same I_T nexus
RAC 0 [cha: n, def: 0, sav: 0] Report a check
UA_INTLCK 0 [cha: n, def: 0, sav: 0] Unit attention interlocks control
0: unit attention cleared with check condition status
2: unit attention not cleared with check condition status
3: as 2 plus ua on busy, task set full or reservation conflict
SWP 0 [cha: n, def: 0, sav: 0] Software write protect
ATO 0 [cha: n, def: 0, sav: 0] Application tag owner
TAS 0 [cha: n, def: 0, sav: 0] Task aborted status
0: tasks aborted without response to app client
1: any other I_T nexuses receive task aborted
So it doesn't support UA_INTLCK ("cha: n" implies the user
cannot change that value). QAM can be changed to allow
unrestricted re-ordering (of task with the SIMPLE task
attribute).
The NormACA bit in the standard INQUIRY response is 0 so
it doesn't support ACA either.
Doug Gilbert
next prev parent reply other threads:[~2006-03-14 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 16:21 SCSI target and IO-throttling Vladislav Bolkhovitin
2006-03-03 18:07 ` Steve Byan
2006-03-03 18:47 ` Stefan Richter
2006-03-03 20:24 ` Steve Byan
2006-03-06 19:15 ` Bryan Henderson
2006-03-06 19:55 ` Steve Byan
2006-03-07 23:32 ` Bryan Henderson
2006-03-08 15:35 ` Vladislav Bolkhovitin
2006-03-08 15:56 ` Steve Byan
2006-03-08 17:49 ` Vladislav Bolkhovitin
2006-03-08 18:09 ` Steve Byan
2006-03-09 18:37 ` Vladislav Bolkhovitin
2006-03-09 19:32 ` Steve Byan
2006-03-10 18:46 ` Vladislav Bolkhovitin
2006-03-10 19:47 ` Steve Byan
2006-03-13 17:35 ` Vladislav Bolkhovitin
2006-03-14 20:54 ` Douglas Gilbert [this message]
2006-03-15 17:15 ` Vladislav Bolkhovitin
2006-03-10 13:26 ` Steve Byan
2006-03-07 17:56 ` Vladislav Bolkhovitin
2006-03-07 18:38 ` Steve Byan
2006-03-07 17:53 ` Vladislav Bolkhovitin
2006-03-07 18:19 ` Steve Byan
2006-03-07 18:46 ` Vladislav Bolkhovitin
2006-03-07 19:00 ` Steve Byan
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=44172D88.6070201@torque.net \
--to=dougg@torque.net \
--cc=hbryan@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=smb@egenera.com \
--cc=vst@vlnb.net \
/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).