RW Queue Bypass
Common Options : Auto, 2X, 4X, 8X, 16X
Quick Review of RW Queue Bypass
The RW Queue Bypass BIOS setting determines how many times the arbiter is allowed to bypass the oldest memory access request in the DCI’s read/write queue.
Once this limit is reached, the arbiter is overriden and the oldest memory access request serviced instead.
As this feature greatly improves memory performance, most BIOSes will not include a Disabled setting.
Instead, you are allowed to adjust the number of times the arbiter is allowed to bypass the oldest memory access request in the queue.
A high bypass limit will give the arbiter more flexibility in scheduling memory accesses so that it can maximise the number of hits on open memory pages.
This improves the performance of the memory subsystem. However, this comes at the expense of memory access requests that get delayed. Such delays can be a problem for time-sensitive applications.
It is generally recommended that you set the RW Queue Bypass BIOS feature to the maximum value of 16X, which would give the memory controller’s read-write queue arbiter maximum flexibility in scheduling memory access requests.
However, if you face stability issues, especially with time-sensitive applications, reduce the value step-by-step until the problem resolves.
The Auto option, if available, usually sets the bypass limit to the maximum – 16X.
Details of RW Queue Bypass
The R/W Queue Bypass BIOS option is similar to the DCQ Bypass Maximum BIOS option – they both decide the limits on which an arbiter can intelligently reschedule memory accesses to improve performance.
The difference between the two is that DCQ Bypass Maximum does this at the memory controller level, while R/W Queue Bypass does it at the Device Control Interface (DCI) level.
To improve performance, the arbiter can reschedule transactions in the DCI read / write queue.
By allowing some transactions to bypass other transactions in the queue, the arbiter can maximize the number of hits on open memory pages.
This improves the overall memory performance but at the expense of some memory accesses which have to be delayed.
The RW Queue Bypass BIOS setting determines how many times the arbiter is allowed to bypass the oldest memory access request in the DCI’s read/write queue.
Once this limit is reached, the arbiter is overriden and the oldest memory access request serviced instead.
As this feature greatly improves memory performance, most BIOSes will not include a Disabled setting.
Instead, you are allowed to adjust the number of times the arbiter is allowed to bypass the oldest memory access request in the queue.
A high bypass limit will give the arbiter more flexibility in scheduling memory accesses so that it can maximise the number of hits on open memory pages.
This improves the performance of the memory subsystem. However, this comes at the expense of memory access requests that get delayed. Such delays can be a problem for time-sensitive applications.
It is generally recommended that you set this BIOS feature to the maximum value of 16X, which would give the memory controller’s read-write queue arbiter maximum flexibility in scheduling memory access requests.
However, if you face stability issues, especially with time-sensitive applications, reduce the value step-by-step until the problem resolves.
The Auto option, if available, usually sets the bypass limit to the maximum – 16X.
Recommended Reading
[adrotate group=”2″]- AGP Capability from The Tech ARP BIOS Guide
- PCI Clock Synchronization Mode – The Tech ARP BIOS Guide
- CPU Drive Strength from The Tech ARP BIOS Guide
- Multi-Sector Transfers from The Tech ARP BIOS Guide
- PCI Chaining from The Tech ARP BIOS Guide
- PCI-E Max Read Request Size – The Tech ARP BIOS Guide
- PPM Mode from The Tech ARP BIOS Guide
- SDRAM PH Limit from the Tech ARP BIOS Guide
- MP Capable Bit Identify from The Tech ARP BIOS Guide
Go Back To > The Tech ARP BIOS Guide | Home
Support Tech ARP!
If you like our work, you can help support our work by visiting our sponsors, participating in the Tech ARP Forums, or even donating to our fund. Any help you can render is greatly appreciated!