Host command queue mode, End device frame buffering, Pcie command queue depth – Areca 24/4 Internal/External Port Pcie 3.0 12 Gb/s SAS/SATA Raid Controller 2Gb Cache User Manual
Page 193: Write cache amount, Save sed key in controller, Web browser-based configuration
193
WEB BROWSER-BASED CONFIGURATION
• Host Command Queue Mode
This option is used to solve the the problem with reads stalling
that causes by out of order command completion. Choose the
“Host Command Queue Mode” option=”Ordered” on the “Ad
-
vanced Configuration” if you want similar read/write through
-
puts. There the read and write get the same priority as they are
scheduled and the reads are not pushed back.
• End Device Frame Buffering
Using the 12Gb/s SAS technology, including End Device Frame
Buffering (EDFB) technology, the ROC and expander are de
-
signed to help ease the industry’s transition to12Gb/s SAS-
enabled systems by enabling customers to take advantage of
12Gb/s speeds while using existing 6Gb/s drives and backplane
infrastructure. This technology allows the expander to perform
aggregation, essentially allowing two devices to share one port
on the expander.
• PCIe Command Queue Depth
This parameter is adjusted the commands per queue of PCIe
bus which transmits multiple commands to a single target with-
out waiting for the initial command to complete. User can set
the “PCIe Command Queue Depth” to 256, 512, or 1024.
• Write Cache Amount
The “Write Cache Amount” is for controller to configure how
much cache SDRAM dedicated for read, and how much for
write. By default (Unified), the size of read or write cache
is automatically assigned by the controller firmware. If your
server application has significantly more reads than writes or
more writes than reads, you might need to change this setting
to adjust the read/write cache ratio for improving performance.
Reboot is required for the setting to take effect. The optimal
ratio setting is application-dependent.
• Save SED Key In Controller
<a> If enable --> disable, clear SED Key saved in setup
<b> If disable --> enable, if key exists, save to setup
If enable--->disable, the key will not remain in the flash. So
that next time power up again, it will need to input the key
from the CLI or McRAID manager. You can also import the key