Fujitsu MAP3147 Scsi Logical Interface Specifications page 202

Scsi logical interface specifications 3.5 inch hard disk drives with internal scsi controller
Table of Contents

Advertisement

Parameter Data Formats
"1" : Requests that the device server not read into the buffer any logical blocks beyond the
addressed logical blocks.
"0" : The device server continues to read logical blocks into the buffer beyond the addressed
logical blocks.
n. FSW (force sequential write) (not supported)
This bit specifies how to write multiple blocks.
"1" : If the IDD writes multiple blocks, this indicates that data are recorded on the disk media in
the order in which they are transferred from the INIT.
"0" : If the IDD writes multiple blocks, this indicates that data are recorded on the disk media
with their order changed in order to complete the command in the fastest time.
This bit cannot be changed. The IDD disregards the specification in this bit and operates
according to the "Default" value (="1").
o. LBCSS (Logical Block Cache Segment Size) (not supported)
"1" : Indicates that the "Cache segment size" field units are interpreted as logical blocks.
"0" : The "Cache segment size" field units are interpreted as bytes.
This bit is not supported for the IDD. The IDD disregards the specification in this bit.
p. Cache segment count
This parameter specifies the number of cache segments used by the IDD. This parameter is valid
when the SIZE bit specification is "0."
When a value greater than max value is specified, the IDD performs rounding processing and
sets max value. Also, when a value less than 3 is specified, the IDD performs rounding
processing and set 4.
This parameter indicates the same value for all initiators and if it is changed by any initiator, a
UNIT ATTENTION condition (UNIT ATTENTION [=6] / Mode select parameter changed
[=2A-01]) is generated for all the initiators that did not change it.
This parameter can be changed though the IDD disregards the specification of this field. The
IDD divides the Cache Segments according to the inherent algorithm. That is, the Cache
Segment size is best tuned per the request data size of Host command. Within one Cache
Segment, data for various commands are stored.
approximately 476 KB.
IDD does not support this paramenter. IDD disregards the specification of this field.
q. Non cache buffer size
If this field is greater than zero, this field advises the device server how many bytes the
application client requests that the device server allocate for a buffer function when all other
4 - 26
The biggest Cache Segment size is
C141-E167

Advertisement

Table of Contents
loading

Table of Contents