Lines Matching refs:queue

7 CFQ maintains the per process queue for the processes which request I/O
19 queue is expired and CFQ selects next queue to dispatch from.
72 queue level. This was introduced after a bottleneck was observed
73 in higher end storage due to idle on sequential queue and allow dispatch
74 from a single queue. The idea with this parameter is that it can be run with
101 time for each process to issue I/O request before the cfq queue is switched.
112 This parameter is same as of slice_sync but for asynchronous queue. The
118 device request queue in queue's slice time. The maximum number of request that
124 When a queue is selected for execution, the queues IO requests are only
126 queue. This parameter is used to calculate the time slice of synchronous
127 queue.
131 time_slice of synchronous queue, increase the value of slice_sync. Default
136 This specifies the number of request dispatched to the device queue. In a
137 queue's time slice, a request will not be dispatched if the number of request
210 request queue at a time. In such scenario, it is not possible to measure time
211 consumed by single queue accurately.
214 single queue and also allow dispatch from multiple cfq queue at the same time.
225 Idling on a queue is primarily about waiting for the next request to come
226 on same queue after completion of a request. In this process CFQ will not
232 one), then not dispatching request from other queue should help as we
234 one queue.
241 On this tree we idle on each queue individually.
247 we will idle only once last queue has dispatched the IO and there is
254 media which can support higher queue depth (multiple requests at in