Lines Matching refs:interactive
38 * and yet guarantee a low latency to interactive and soft real-time
43 * applications: interactive and soft real-time. In more detail, BFQ
49 * the I/O requests in a bfq_queue come from an interactive or a soft
51 * said to be interactive or soft real-time. In both cases, BFQ
52 * privileges the service of the queue, over that of non-interactive
56 * queue is privileged, because deemed interactive or soft real-time.
61 * interactive queue works as follows: a queue is deemed interactive
64 * interactive again (for a limited time), if it restarts being
70 * non-empty queue stops being deemed interactive. Since a queue is
71 * weight-raised while it is deemed interactive, this maximum time
73 * weight-raising for interactive queues.
91 * ones that guarantee a low latency to interactive and soft real-time
272 * for interactive queues automatically (see the comments at the
285 * weight raising to interactive applications.
314 * privilege interactive tasks. This mechanism is vulnerable to the
329 * interactive tasks is computed.
331 * For a bfq_queue deemed as interactive, the duration of weight
334 * execute the 'largest' interactive task we benchmarked so far. By
337 * reference interactive task is the start-up of LibreOffice Writer,
361 * during which interactive false positives cause the two problems
999 * responsiveness by allowing non-interactive applications to
1003 * difficult for most interactive tasks to complete their jobs
1009 /* switch back from soft real-time to interactive weight raising */
1193 * Unfortunately, false positives may occur while an interactive task
1198 * start doing I/O exactly when the interactive task starts.
1526 bool interactive,
1532 if (interactive) {
1538 * No interactive weight raising in progress
1543 * now, no interactive weight-raising period
1569 if (interactive) { /* update wr coeff and duration */
1590 * 2) since the application is not interactive,
1662 bool *interactive)
1690 *interactive = !in_burst && idle_for_long_time;
1694 bfqq->bic && (*interactive || soft_rt)));
1706 * idle for much more than an interactive queue, then we
1750 *interactive,
1878 bool interactive = false;
2076 rq, &interactive);
2106 * . if bfqq is interactive, because, regardless of whether
2119 (old_wr_coeff == 1 || bfqq->wr_coeff == 1 || interactive))
2741 * would have deserved interactive weight raising, but
3457 * differentiate between interactive weight raising and soft real-time
3999 * interactive weight raising. We do not do it in the
4006 * interactive bfqq, and bfqq had received a lot of
5703 * do not compute soft_rt_next_start if bfqq is in interactive