|
|
|
|||||||
|
|
||||||||
|
|
|
|
|
|||||
| Home | ||||||||
| Free Downloads | ||||||||
| Product FAQs (NT) | ||||||||
| Product FAQs (OpenVMS) | ||||||||
| Product Alerts | ||||||||
| Technical References | ||||||||
| Links | ||||||||
|
||||||||
|
When I/O Express extends the pool, how does the size of the pool get reduced?When I/O Express extends the non-paged pool, it will hold onto that pool until the system is rebooted. There is a point at which I/O Express will no longer extend the pool, but I/O Express will keep the pool once it gets it. I/O Express uses non-paged pool for data structures, which point to pages in the cache. These are the data structures that are searched when I/O Express intercepts a read I/O, to determine if the requested data is in cache or not. If it is, I/O Express redirects the I/O to the cache; if not, I/O Express lets it pass through to the disk queue.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
||||||||
|
|
Executive Software Europe |
|
||||||