Lines Matching refs:request

7 CFQ maintains the per process queue for the processes which request I/O
17 This specifies how long CFQ should idle for next request on certain cfq queues
52 backward distance of request is just 1/back_seek_penalty from a "front"
53 request, then the seeking cost of two requests is considered equivalent.
55 So scheduler will not bias toward one or the other request (otherwise scheduler
56 will bias toward front request). Default value of back_seek_penalty is 2.
101 time for each process to issue I/O request before the cfq queue is switched.
117 This parameter is used to limit the dispatching of asynchronous request to
118 device request queue in queue's slice time. The maximum number of request that
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
139 request.
142 processing of request. Therefore, increasing the value can improve the
210 request queue at a time. In such scenario, it is not possible to measure 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
244 request which are marked with REQ_NOIDLE go on this service tree. On this
269     100ms each. If a REQ_NOIDLE request comes in, it will be scheduled
270     roughly after 1 second. If after completion of REQ_NOIDLE request we
272     request comes in, again it will be scheduled after 1second. Repeat it