Lines Matching full:plugging

842  * of this function is used to check whether I/O-dispatch plugging can
1977 	 * says no, then plugging is not needed any longer, either to  in bfq_bfqq_handle_idle_busy_switch()
1979 	 * the best option is to stop plugging I/O, as not doing so  in bfq_bfqq_handle_idle_busy_switch()
2134  * first I/O-plugging time interval for bfqq. This triggers the first
2137  * during the next I/O-plugging interval for bfqq.
2986 	 * plugging most of the time. This evidently makes it harder  in bfq_setup_cooperator()
3729  * idling (I/O-dispatch plugging) is certainly needed to guarantee
3859  * plugging I/O dispatching minimizes the delay induced by already
3865  * unlucky scenario: if I/O-dispatch plugging is (correctly) disabled
3875  * plugging for a special symmetric case that may suddenly turn into
3926 	 * bfqq if it needs I/O-dispatch plugging, even if it is  in __bfq_bfqq_expire()
4691 	 * - a lot of time has elapsed since the plugging of I/O  in bfq_choose_bfqq_for_injection()
4983 		 * I/O-plugging timeout fires. So one may deem the  in bfq_select_queue()
4994 		 * fourth alternative, the duration of the plugging,  in bfq_select_queue()
5724  * counterproductive action with these workloads is plugging I/O
5728  * To avoid this plugging, BFQ has been using a burst-handling
5982 	 * think time with half the I/O-plugging timeout.  in bfq_update_has_short_ttime()
6022 	 * I/O-dispatch-plugging, then bfqq remains empty, and no I/O  in bfq_update_has_short_ttime()
6066 	 * more frequently than once per I/O-plugging timeout, makes  in bfq_update_has_short_ttime()
6472 			 * (I/O-dispatch plugging).  in bfq_completed_request()