Lines Matching refs:dispatch
66 * Order clearing SCHED_RESTART and list_empty_careful(&hctx->dispatch)
68 * blk_mq_dispatch_rq_list(). So dispatch code won't see SCHED_RESTART,
69 * meantime new request added to hctx->dispatch is missed to check in
97 goto dispatch;
103 dispatch:
114 * Returns -EAGAIN if hctx->dispatch was found non-empty and run_work has to
138 if (!list_empty_careful(&hctx->dispatch)) {
152 * same queue and if we didn't dispatch then there's
179 * dispatch batching requests from same hctx at a time.
228 * Returns -EAGAIN if hctx->dispatch was found non-empty and run_work has to
240 if (!list_empty_careful(&hctx->dispatch)) {
257 * same queue and if we didn't dispatch then there's
272 /* round robin for fair dispatch */
290 * If we have previous entries on our dispatch list, grab them first for
291 * more fair dispatch.
293 if (!list_empty_careful(&hctx->dispatch)) {
295 if (!list_empty(&hctx->dispatch))
296 list_splice_init(&hctx->dispatch, &rq_list);
302 * requests from the dispatch list. This is to avoid the case where
303 * we only ever dispatch a fraction of the requests available because
309 * We want to dispatch from the scheduler if there was nothing
310 * on the dispatch list or we were able to dispatch from the
311 * dispatch list.
345 * A return of -EAGAIN is an indication that hctx->dispatch is not
408 * dispatch flush and passthrough rq directly
410 * passthrough request has to be added to hctx->dispatch directly.
413 * FS request will be added to hctx->dispatch. However passthrough
416 * chance to dispatch it given we prioritize requests in hctx->dispatch.
440 * sw queue, meantime we add flush request to dispatch queue(
441 * hctx->dispatch) directly and there is at most one in-flight
443 * flush request to tail or front of the dispatch queue.
448 * rq to the front of hctx->dispatch, it is easier to introduce
450 * compared with adding to the tail of dispatch queue, then
454 * drive when adding flush rq to the front of hctx->dispatch.
456 * Simply queue flush rq to the front of hctx->dispatch so that