Lines Matching refs:sequential
18 (for sequential workloads) and service trees (for random workloads) before
73 in higher end storage due to idle on sequential queue and allow dispatch
99 latency. But if sequential workload is higher(e.g. sequential read),
231 sequential reads (next read will come on only after completion of previous
233 did not move the disk head and kept on dispatching sequential IO from
240 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
243 All synchronous non-sequential queues go on sync-noidle tree. Also any
265 queues. Otherwise in presence of many sequential readers, other
268 For example, if there are 10 sequential readers doing IO and they get
274 multiple sequential readers.
282 badly in presence of multiple sequential readers.
285 provides isolation from multiple sequential readers and at the same