Seagate ST300MP0004 Savvio 15K.1 SAS Product Manual - Page 19

Cache operation

Page 19 highlights

All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this drive family are given in Table 9. 4.5 Cache operation Note. Refer to the SAS Interface Manual for more detail concerning the cache bits. Of the 16 Mbytes physical buffer space in the drive, approximately 13,000 kbytes can be used as a cache. The buffer is divided into logical segments 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 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. All data transfers to the host are in accordance with 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 all of the requested logical blocks are already in the cache: 1. Drive transfers the requested logical blocks to the initiator. Case B-A Read command requests data, and at least one requested 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. Each cache segment is actually a self-contained circular buffer whose length is an integer number of logical blocks. The drive dynamically creates and removes segments based on the workload. The wrap-around capability of the individual segments greatly enhances the cache's overall performance. Note. The size of each segment is not reported by Mode Sense command page 08h, bytes 14 and 15. The value 0XFFFF is always reported regardless of the actual size of the segment. Sending a size specification using the Mode Select command (bytes 14 and 15) does not set up a new segment size. If the STRICT bit in Mode page 00h (byte 2, bit 1) is set to one, the drive responds as it does for any attempt to change an unchangeable parameter. 4.5.1 Caching write data Write caching is a write operation by the drive that makes use of a drive buffer storage area where the data to be written to the medium is stored while the drive performs the Write command. If read caching is enabled (RCD=0), then data written to the medium is retained in the cache to be made available for future read cache hits. The same buffer space and segmentation is used as set up for read functions. The buffer segmentation scheme is set up or changed independently, having nothing to do with the state of RCD. When a write command is issued, if RCD=0, the cache is first checked to see if any logical blocks that are to be written are already stored in the cache from a previous read or write command. If there are, the respective cache segments are cleared. The new data is cached for subsequent Read commands. If the number of write data logical blocks exceed the size of the segment being written into, when the end of the segment is reached, the data is written into the beginning of the same cache segment, overwriting the data that was written there at the beginning of the operation; however, the drive does not overwrite data that has not yet been written to the medium. Savvio 15K SAS Product Manual, Rev. C 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

Savvio 15K SAS Product Manual, Rev. C
13
All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this
drive family are given in Table 9.
4.5
Cache operation
Note.
Refer to the
SAS Interface Manual
for more detail concerning the cache bits.
Of the 16 Mbytes physical buffer space in the drive, approximately 13,000 kbytes can be used as a cache. The
buffer is divided into logical segments 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 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. All data transfers to the host are in accordance with 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 all of the requested logical blocks are already in the cache:
1.
Drive transfers the requested logical blocks to the initiator.
Case B
—A Read command requests data, and at least one requested 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.
Each cache segment is actually a self-contained circular buffer whose length is an integer number of logical
blocks. The drive dynamically creates and removes segments based on the workload. The wrap-around capa-
bility of the individual segments greatly enhances the cache’s overall performance.
Note.
The size of each segment is not reported by Mode Sense command page 08h, bytes 14 and 15.
The value 0XFFFF is always reported regardless of the actual size of the segment. Sending a size
specification using the Mode Select command (bytes 14 and 15) does not set up a new segment
size. If the STRICT bit in Mode page 00h (byte 2, bit 1) is set to one, the drive responds as it does
for any attempt to change an unchangeable parameter.
4.5.1
Caching write data
Write caching is a write operation by the drive that makes use of a drive buffer storage area where the data to
be written to the medium is stored while the drive performs the Write command.
If read caching is enabled (RCD=0), then data written to the medium is retained in the cache to be made avail-
able for future read cache hits. The same buffer space and segmentation is used as set up for read functions.
The buffer segmentation scheme is set up or changed independently, having nothing to do with the state of
RCD. When a write command is issued, if RCD=0, the cache is first checked to see if any logical blocks that
are to be written are already stored in the cache from a previous read or write command. If there are, the
respective cache segments are cleared. The new data is cached for subsequent Read commands.
If the number of write data logical blocks exceed the size of the segment being written into, when the end of the
segment is reached, the data is written into the beginning of the same cache segment, overwriting the data that
was written there at the beginning of the operation; however, the drive does not overwrite data that has not yet
been written to the medium.