Asus PIKE 2108 PIKE 2108 user's manual - Page 25

Write Back with BBU, Always Write Back

Get Asus PIKE 2108 PDF manuals and user guides View all Asus PIKE 2108 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

◊ A head: This enables read ahead capability, which allows the controller to read sequentially ahead of requested data and to store the additional data in cache memory, anticipating that the data will be needed soon. This speeds up reads for sequential data, but there is little improvement when accessing random data. This is the default. • Write Policy: Specify the write policy for this virtual drive: ◊ W rite Through: In Write Through mode the controller sends a data transfer completion signal to the host when the drive subsystem has received all of the data in a transaction. ◊ A lways Write Back: In Writeback mode the controller sends a data transfer completion signal to the host when the controller cache has received all of the data in a transaction. This setting is recommended in Standard mode. ◊ W rite Back with BBU: In Writeback mode the controller sends a data transfer completion signal to the host when the controller cache has received all of the data in a transaction. This setting has to be used with a Battery Backup Unit (BBU). This is the default. • IO Policy: The IO Policy applies to reads on a specific virtual drive. It does not affect the read ahead cache. ◊ D irect: In direct I/O mode, reads are not buffered in cache memory. Data is transferred to the cache and the host concurrently. If the same data block is read again, it comes from cache memory. ◊ C ached: In cached I/O mode, all reads are buffered in cache memory. This is the default. • Drive Cache: Specify the drive cache policy: ◊ N oChange: Leave the current drive cache policy unchanged. This is the default. ◊ Enable: Enable the drive cache. ◊ D isable: Disable the drive cache. • Disable BGI: Specify the background initialization status: ◊ No: Leave background initialization enabled. This means that a new configuration can be initialized in the background while you use WebBIOS to do other configuration tasks. This is the default. ◊ Y es: Select Yes if you do not want to allow background initializations for configurations on this controller. • Select Size: Specify the size of the virtual drive in terabytes, gigabytes, megabytes, or kilobytes. Normally, this would be the full size for RAID 0 shown in the Configuration panel on the right. You may specify a smaller size if you want to create other virtual drives on the same drive group. ASUS PIKE 2108 2-11

  • 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
ASUS PIKE 2108
2-11
◊
Ahead:
This enables read ahead capability, which allows the
controller to read sequentially ahead of requested data and to store
the additional data in cache memory, anticipating that the data will be
needed soon. This speeds up reads for sequential data, but there is
little improvement when accessing random data. This is the default.
•
Write Policy:
Specify the write policy for this virtual drive:
◊
Write Through:
In Write Through mode the controller sends a data
transfer completion signal to the host when the drive subsystem has
received all of the data in a transaction.
◊
Always Write Back:
In Writeback mode the controller sends a data
transfer completion signal to the host when the controller cache has
received all of the data in a transaction. This setting is recommended
in Standard mode.
◊
Write Back with BBU:
In Writeback mode the controller sends a data
transfer completion signal to the host when the controller cache has
received all of the data in a transaction. This setting has to be used
with a Battery Backup Unit (BBU). This is the default.
•
IO Policy:
The IO Policy applies to reads on a specific virtual drive. It
does not affect the read ahead cache.
◊
Direct:
In direct I/O mode, reads are not buffered in cache memory.
Data is transferred to the cache and the host concurrently. If the same
data block is read again, it comes from cache memory.
◊
Cached:
In cached I/O mode, all reads are buffered in cache memory.
This is the default.
•
Drive Cache:
Specify the drive cache policy:
◊
NoChange:
Leave the current drive cache policy unchanged. This is
the default.
◊
Enable:
Enable the drive cache.
◊
Disable:
Disable the drive cache.
•
Disable BGI
: Specify the background initialization status:
◊
No:
Leave background initialization enabled. This means that a new
configuration can be initialized in the background while you use
WebBIOS to do other configuration tasks. This is the default.
◊
Yes:
Select Yes if you do not want to allow background initializations
for configurations on this controller.
•
Select Size:
Specify the size of the virtual drive in terabytes, gigabytes,
megabytes, or kilobytes. Normally, this would be the full size for RAID 0
shown in the Configuration panel on the right. You may specify a smaller
size if you want to create other virtual drives on the same drive group.