Lines Matching refs:queues

17 This specifies how long CFQ should idle for next request on certain cfq queues
22 queues/service trees. This can be very helpful on highly seeky media like
26 Setting slice_idle to 0 will remove all the idling on queues/service tree
76 queues in the group but happens overall on the group and thus still keeps the
78 Not idling on individual queues in the group will dispatch requests from
79 multiple queues in the group at the same time and achieve higher throughput
123 When a queue is selected for execution, the queues IO requests are only
208 it would be better to dispatch multiple requests from multiple cfq queues in
226 dispatch requests from other cfq queues even if requests are pending there.
235 CFQ has following service trees and various queues are put on these trees.
239 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
242 All synchronous non-sequential queues go on sync-noidle tree. Also any
244 service tree. On this tree we do not idle on individual queues instead idle
245 on the whole group of queues or the tree. So if there are 4 queues waiting
250 queues.
254 flight at a time), then it cuts down on idling of individual queues and
255 all the queues move to sync-noidle tree and only tree idle remains. This
256 tree idling provides isolation with buffered write queues on async tree.
260 Q1. Why to idle at all on queues not marked with REQ_IDLE.
262 A1. We only do tree idle (all queues on sync-noidle tree) on queues not marked
264     queues. Otherwise in presence of many sequential readers, other