Lines Matching refs:dispatch
36 * Order clearing SCHED_RESTART and list_empty_careful(&hctx->dispatch)
38 * blk_mq_dispatch_rq_list(). So dispatch code won't see SCHED_RESTART,
39 * meantime new request added to hctx->dispatch is missed to check in
67 goto dispatch;
73 dispatch:
84 * Returns -EAGAIN if hctx->dispatch was found non-empty and run_work has to
109 if (!list_empty_careful(&hctx->dispatch)) {
124 * same queue and if we didn't dispatch then there's
163 * dispatch batching requests from same hctx at a time.
212 * Returns -EAGAIN if hctx->dispatch was found non-empty and run_work has to
226 if (!list_empty_careful(&hctx->dispatch)) {
244 * same queue and if we didn't dispatch then there's
261 /* round robin for fair dispatch */
276 * If we have previous entries on our dispatch list, grab them first for
277 * more fair dispatch.
279 if (!list_empty_careful(&hctx->dispatch)) {
281 if (!list_empty(&hctx->dispatch))
282 list_splice_init(&hctx->dispatch, &rq_list);
288 * requests from the dispatch list. This is to avoid the case where
289 * we only ever dispatch a fraction of the requests available because
295 * We want to dispatch from the scheduler if there was nothing
296 * on the dispatch list or we were able to dispatch from the
297 * dispatch list.
330 * A return of -EAGAIN is an indication that hctx->dispatch is not