Seagate ST336754SS Cheetah 15K.4 SAS Product Manual - Page 23

Prefetch/multi-segmented cache control, Cache operation

Page 23 highlights

If the drive receives a START STOP UNIT command with the START bit and IMMED bit equal to 1 and does not receive a NOTIFY (ENABLE SPINUP) primitive within 5 seconds, the drive fails the START STOP UNIT command. The START STOP UNIT command may be used to command the drive to stop the spindle. Stop time is 30 seconds (maximum) from removal of DC power. There is no power control switch on the drive. 4.4 Prefetch/multi-segmented cache control The drive provides a prefetch (read look-ahead) and multi-segmented cache control algorithms that in many cases can enhance system performance. Cache refers to the drive buffer storage space when it is used in cache operations. To select this feature, the host sends the Mode Select command with the proper values in the applicable bytes in page 08h. Prefetch and cache operations are independent features from the standpoint that each is enabled and disabled independently using the Mode Select command; however, in actual operation, the prefetch feature overlaps cache operation somewhat as described in sections 4.5.1 and 4.5.2. All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this drive family are given in Table 9.3.2.1. 4.5 Cache operation Note. Refer to the SAS Interface Manual for more detail concerning the cache bits. Of the 8,192 kbytes physical buffer space in the drive, approximately 7,077 kbytes can be used as a cache. The buffer can be divided into logical segments (using Mode Select Page 08h, byte 13) from which data is read and to which data is written. The drive keeps track of the logical block addresses of the data stored in each segment of the buffer. If the cache is enabled (see RCD bit in the SAS Interface Manual), data requested by the host with a read command is retrieved from the buffer, if possible, before any disc access is initiated. If cache operation is not enabled, the buffer (still segmented with the required number of segments) is still used, but only as circular buffer segments during disc medium read operations (disregarding Prefetch operation for the moment). That is, the drive does not check in the buffer segments for the requested read data, but goes directly to the medium to retrieve it. The retrieved data merely passes through some buffer segment on the way to the host. On a cache miss, all data transfers to the host are in accordance with buffer-full ratio rules. On a cache hit, the drive ignores the bufferfull ratio rules. See the explanation provided with the information about Mode Page 02h (disconnect/reconnect control) in the SAS Interface Manual. The following is a simplified description of the prefetch/cache operation: Case A-read command is received and the first logical block is already in the cache: 1. Drive transfers to the initiator the first logical block requested plus all subsequent contiguous logical blocks that are already in the cache. This data may be in multiple segments. 2. When a requested logical block is reached that is not in any cache segment, the drive fetches it and any remaining requested logical block addresses from the disc and puts them in a segment of the cache. The drive transfers the remaining requested logical blocks from the cache to the host in accordance with the Mode Select Disconnect/Reconnect parameters, page 02h. 3. If the prefetch feature is enabled, refer to section 4.5.2 for operation from this point. Case B-A Read command requests data, and the first logical block is not in any segment of the cache: 1. The drive fetches the requested logical blocks from the disc and transfers them into a segment, and then from there to the host in accordance with the Mode Select Disconnect/Reconnect parameters, page 02h. 2. If the prefetch feature is enabled, refer to section 4.5.2 for operation from this point. Cheetah 15K.4 SAS Product Manual, Rev. B 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94

Cheetah 15K.4 SAS Product Manual, Rev. B
13
If the drive receives a START STOP UNIT command with the START bit and IMMED bit equal to 1 and does
not receive a NOTIFY (ENABLE SPINUP) primitive within 5 seconds, the drive fails the START STOP UNIT
command.
The START STOP UNIT command may be used to command the drive to stop the spindle. Stop time is 30 sec-
onds (maximum) from removal of DC power. There is no power control switch on the drive.
4.4
Prefetch/multi-segmented cache control
The drive provides a prefetch (read look-ahead) and multi-segmented cache control algorithms that in many
cases can enhance system performance. Cache refers to the drive buffer storage space when it is used in
cache operations. To select this feature, the host sends the Mode Select command with the proper values in
the applicable bytes in page 08h. Prefetch and cache operations are independent features from the standpoint
that each is enabled and disabled independently using the Mode Select command; however, in actual opera-
tion, the prefetch feature overlaps cache operation somewhat as described in sections 4.5.1 and 4.5.2.
All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this
drive family are given in Table 9.3.2.1.
4.5
Cache operation
Note.
Refer to the
SAS Interface Manual
for more detail concerning the cache bits.
Of the 8,192 kbytes physical buffer space in the drive, approximately 7,077 kbytes can be used as a cache.
The buffer can be divided into logical segments (using Mode Select Page 08h, byte 13) from which data is read
and to which data is written.
The drive keeps track of the logical block addresses of the data stored in each segment of the buffer. If the
cache is enabled (see RCD bit in the
SAS Interface Manual
), data requested by the host with a read command
is retrieved from the buffer, if possible, before any disc access is initiated. If cache operation is not enabled, the
buffer (still segmented with the required number of segments) is still used, but only as circular buffer segments
during disc medium read operations (disregarding Prefetch operation for the moment). That is, the drive does
not check in the buffer segments for the requested read data, but goes directly to the medium to retrieve it. The
retrieved data merely passes through some buffer segment on the way to the host. On a cache miss, all data
transfers to the host are in accordance with buffer-full ratio rules. On a cache hit, the drive ignores the buffer-
full ratio rules. See the explanation provided with the information about Mode Page 02h (disconnect/reconnect
control) in the
SAS Interface Manual
.
The following is a simplified description of the prefetch/cache operation:
Case A
—read command is received and the first logical block is already in the cache:
1.
Drive transfers to the initiator the first logical block requested plus all subsequent contiguous logical blocks
that are already in the cache. This data may be in multiple segments.
2.
When a requested logical block is reached that is not in any cache segment, the drive fetches it and any
remaining requested logical block addresses from the disc and puts them in a segment of the cache. The
drive transfers the remaining requested logical blocks from the cache to the host in accordance with the
Mode Select Disconnect/Reconnect parameters, page 02h.
3.
If the prefetch feature is enabled, refer to section 4.5.2 for operation from this point.
Case B
—A Read command requests data, and the first logical block is not in any segment of the cache:
1.
The drive fetches the requested logical blocks from the disc and transfers them into a segment, and then
from there to the host in accordance with the Mode Select Disconnect/Reconnect parameters, page 02h.
2.
If the prefetch feature is enabled, refer to section 4.5.2 for operation from this point.