Searched refs:REQ_NOIDLE (Results 1 – 5 of 5) sorted by relevance
244 request which are marked with REQ_NOIDLE go on this service tree. On this261 Q1. Why to idle at all on queues marked with REQ_NOIDLE.264 with REQ_NOIDLE. This helps in providing isolation with all the sync-idle269 100ms each. If a REQ_NOIDLE request comes in, it will be scheduled270 roughly after 1 second. If after completion of REQ_NOIDLE request we271 do not idle, and after a couple of milli seconds a another REQ_NOIDLE280 thread due to REQ_NOIDLE, then next journaling write will not get284 Hence doing tree idling on threads using REQ_NOIDLE flag on requests288 Q2. When to specify REQ_NOIDLE291 to specify REQ_NOIDLE on writes and that probably should work well for
204 #define REQ_NOIDLE (1ULL << __REQ_NOIDLE) macro211 REQ_DISCARD | REQ_WRITE_SAME | REQ_NOIDLE | REQ_FLUSH | REQ_FUA | \
202 #define WRITE_SYNC (WRITE | REQ_SYNC | REQ_NOIDLE)204 #define WRITE_FLUSH (WRITE | REQ_SYNC | REQ_NOIDLE | REQ_FLUSH)205 #define WRITE_FUA (WRITE | REQ_SYNC | REQ_NOIDLE | REQ_FUA)206 #define WRITE_FLUSH_FUA (WRITE | REQ_SYNC | REQ_NOIDLE | REQ_FLUSH | REQ_FUA)
152 rw |= REQ_SYNC | REQ_NOIDLE; in _drbd_md_sync_page_io()
3895 if (cfqq->next_rq && (cfqq->next_rq->cmd_flags & REQ_NOIDLE)) in cfq_update_idle_window()4176 !!(rq->cmd_flags & REQ_NOIDLE)); in cfq_completed_request()