Lines Matching full:idling

185       a new request in time. Device idling typically boosts the
188       addition, under BFQ, device idling is also instrumental in
193       - With respect to idling for service guarantees, if several
197 	idling the device. Throughput is thus as high as possible in
201        (typically NCQ), device idling happens to be always detrimental
202        to throughput. So, with these devices, BFQ performs idling
221   - BFQ automatically deactivates idling for queues born in a burst of
284   guarantees the expected throughput distribution without ever idling
332 slice_idle is a non-zero value. Idling has a double purpose: boosting
337 As for throughput, idling can be very helpful on highly seeky media
341 Setting slice_idle to 0 will remove all the idling on queues and one
355 Idling is however necessary to have service guarantees enforced in
358 requests served for each request served for another queue B. Idling
362 before the next request of B is dispatched. Note that idling
368 There is an important flip side to idling: apart from the above cases
369 where it is beneficial also for throughput, idling can severely impact
371 issue, BFQ tends to avoid idling as much as possible, when it is not
385 Either tunable can be used to set idling behavior.  Afterwards, the
393 - always performs idling when the in-service queue becomes empty;