Fujitsu MHT2030AT Manual/User Guide - Page 237

Read-ahead Cache, read-ahead operation, a transfer of the read requested data starts while the read

Page 237 highlights

6.4 Read-ahead Cache 4) The following cache valid data is for the read command that is executed next: Cache valid data LAST LBA START LBA 6.4.3.3 Full hit In this situation, all read requested data is stored in the data buffer. Transfer of the read requested data is started from the location where hit data is stored. For data that is a target of caching and remains before a full hit, the data is retained when execution of the command is completed. This is done so that a new readahead operation is not performed. If the full hit command is received during the read-ahead operation, a transfer of the read requested data starts while the readahead operation is in progress. 1) An example is the state shown below where the previous read command is executing sequential reading. First, HAP is set at the location where hit data is stored. HAP end location of the previous read command HAP HAP (It is reset to the hit data location for transfers.) Cache data Full hit data Cache data DAP DAP end location of the previous read command 2) The read requested data is transferred, and a new read-ahead operation is not performed. Cache data Full hit data HAP (stop) Cache data C141-E192-02EN 6-17

  • 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
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256

6.4
Read-ahead Cache
C141-E192-02EN
6-17
4)
The following cache valid data is for the read command that is executed next:
Cache valid data
START LBA
LAST LBA
6.4.3.3 Full hit
In this situation, all read requested data is stored in the data buffer.
Transfer of
the read requested data is started from the location where hit data is stored.
For
data that is a target of caching and remains before a full hit, the data is retained
when execution of the command is completed.
This is done so that a new read-
ahead operation is not performed.
If the full hit command is received during the
read-ahead operation, a transfer of the read requested data starts while the read-
ahead operation is in progress.
1)
An example is the state shown below where the previous read command is
executing sequential reading.
First, HAP is set at the location where hit data
is stored.
HAP (It is reset to the hit data location for transfers.)
HAP end location of the previous read command
DAP end location of the previous read command
Cache data
Full hit data
Cache data
HAP
DAP
2)
The read requested data is transferred, and a new read-ahead operation is not
performed.
(stop)
HAP
Cache data
Full hit data
Cache data