Recent Features
| |||||||||||||
Modular, switchable I/O schedulersModular, switchable I/O schedulersPosted Sep 28, 2004 20:32 UTC (Tue) by manpreet (guest, #12039)Parent article: Modular, switchable I/O schedulers
Waiting for the queue to empty out could be a long wait for the threads that want disk attention. Another possible way is to keep accepting requests, but queue them in the new scheduler's queue and switch queues as soon as the older one empties out.
(Log in to post comments)
Modular, switchable I/O schedulers Posted Sep 30, 2004 7:30 UTC (Thu) by axboe (subscriber, #904) [Link] That's not easily doable, since each queue can only have one io scheduler assigned and active. Additionally, the io scheduler requires exclusive access to the given queue. What you propose would require the old one be active from io completions and the new one working for submission and queueing.
Modular, switchable I/O schedulers Posted Oct 6, 2004 10:10 UTC (Wed) by danielos (subscriber, #6053) [Link] it is the same! does not matter what is in the new queue if new scheduler is not active, it is as process are waiting. Another way is to have more scheduler per I/O like process scheduler, but this is an unusefull overload. I don't think it's a matter of changing I/O scheduler seconds by seconds, but, at worst hour by hour, and the thread that want disk attention have to respect other request and scheduler queue policy (or does it exists a super policy that all scheduler respect? this would be a viable way to define a complex but efficent policy and subpolicy).
dan.
|
|||||||||||||