Lines Matching refs:idle
17 This specifies how long CFQ should idle for next request on certain cfq queues
21 By default slice_idle is a non-zero value. That means by default we idle on
73 in higher end storage due to idle on sequential queue and allow dispatch
238 sync-idle sync-noidle async
240 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
241 On this tree we idle on each queue individually.
245 tree we do not idle on individual queues instead idle on the whole group
247 we will idle only once last queue has dispatched the IO and there is
256 all the queues move to sync-noidle tree and only tree idle remains. This
261 Q1. Why to idle at all on queues marked with REQ_NOIDLE.
263 A1. We only do tree idle (all queues on sync-noidle tree) on queues marked
264 with REQ_NOIDLE. This helps in providing isolation with all the sync-idle
271 do not idle, and after a couple of milli seconds a another REQ_NOIDLE
279 that seemed to be the case). Now if one decides not to idle on fsync
286 time we do not idle on individual threads.