Helge Hafting wrote:
Something similiar could be done for io niceness. If we run out of
normal priority io, how about not issuing the low priority io
right away. Anticipate there will be more high-priority io
and wait for some idle time before letting low-priority
requests through. And of course some maximum wait to prevent
total starvation.
The problem is quite similar to scheduling for quality on a network
device. Once a packet has started going it, usually you cannot abort
the packet for a higher priority one.
I thought there was a CBQ I/O scheduling patch or such to offer some
kind of I/O niceness these days?