MF, Multiplication Factor determines how the Maximum Pre-fetch field is interpreted. When this bit is
set the data to pre-fetch is given by the command length multiplied by the value in the Maximum Pre-
fetch field. When this bit is reset the value in the Maximum pre-fetch field is used as the absolute length
to pre-fetch.
RCD, Read Cache Disable bit, of zero indicates that the file may return data requested by a R E A D
command by accessing either the cache or the Read Ahead Buffer, or media. A R C D bit of one indi-
cates that the file shall transfer all data requested by a R E A D command by accessing the media (i.e.,
data cannot be transferred from the cache or Read Ahead Buffer).
Read Retention Priority, Demand Read Retention Priority is not supported.
Write Retention Priority, Write Retention Priority is not supported.
Disable Pre-fetch Transfer Length specifies a number of LBA's which if a read command length exceeds
will cause the drive not to perform read ahead buffering after the command has completed. A value of
zero specifies read ahead is disabled.
Minimum Pre-fetch specifies the minimum number of LBA's that the drive should read ahead after each
read command. A value of zero indicates that read ahead should be terminated immediately a new
command arrives, except in the case when the new command is on the current head and track.
Maximum Pre-fetch specifies the maximum number of LBA's to read ahead after a read command. This
field can either be used as an absolute value, if the M F bit is 0, or else it will be multiplied by the read
command length to give the actual length to read ahead.
Maximum Pre-fetch ceiling specifies the maximum number of blocks the drive should attempt to read
ahead. It is particularly relevant when the M F bit is set.
Number of Cache Segments This field is used to indicate to the drive how many segments are requested
by the initiator. The target supports following Cache Segment configuration:
Note: When the Number of Cache Segments is set to 1, Tagged Command Queuing will be disabled
automatically and the multi-initiator environment will not be supported. If the Tagged Command
Queuing need to be supported, Number of Cache Segments 3 or 7 shall be selected.
Number of Seg-
ments
Segment Size
1
448K
3
128K
7
64K
114
O E M Spec. of DCAS-34330/32160
Summary of Contents for DCAS-32160 - Ultrastar 2.1 GB Hard Drive
Page 2: ......
Page 14: ...xii OEM Spec of DCAS 34330 32160...
Page 16: ...2 OEM Spec of DCAS 34330 32160...
Page 18: ...4 OEM Spec of DCAS 34330 32160...
Page 19: ...Part 1 Functional Specification Copyright IBM Corp 1996 5...
Page 20: ...6 OEM Spec of DCAS 34330 32160...
Page 22: ...8 OEM Spec of DCAS 34330 32160...
Page 32: ...18 OEM Spec of DCAS 34330 32160...
Page 34: ...20 OEM Spec of DCAS 34330 32160...
Page 56: ...6 7 1 2 68 pin Model Figure 35 Outline of 68 pin Model 42 OEM Spec of DCAS 34330 32160...
Page 57: ...6 7 1 3 80 pin Model Figure 36 Outline of 80 pin Model Specification 43...
Page 61: ...6 7 3 3 80 pin Model Figure 41 Interface Connector 80 pin Model Specification 47...
Page 70: ...56 OEM Spec of DCAS 34330 32160...
Page 71: ...Part 2 SCSI Interface Specification Copyright IBM Corp 1996 57...
Page 72: ...58 OEM Spec of DCAS 34330 32160...
Page 176: ...162 OEM Spec of DCAS 34330 32160...
Page 178: ...164 OEM Spec of DCAS 34330 32160...
Page 198: ...184 OEM Spec of DCAS 34330 32160...
Page 218: ...204 OEM Spec of DCAS 34330 32160...
Page 228: ...214 OEM Spec of DCAS 34330 32160...
Page 232: ...IBML Part Number 73H7993 Published in Japan S73H 7993 03...