Home
last modified time | relevance | path

Searched refs:REQ_IDLE (Results 1 – 9 of 9) sorted by relevance

/Linux-v4.19/Documentation/block/
Dcfq-iosched.txt243 synchronous write request which is not marked with REQ_IDLE goes on this
260 Q1. Why to idle at all on queues not marked with REQ_IDLE.
263 with REQ_IDLE. This helps in providing isolation with all the sync-idle
268 100ms each. If a !REQ_IDLE request comes in, it will be scheduled
269 roughly after 1 second. If after completion of !REQ_IDLE request we
270 do not idle, and after a couple of milli seconds a another !REQ_IDLE
279 thread due to !REQ_IDLE, then next journaling write will not get
283 Hence doing tree idling on threads using !REQ_IDLE flag on requests
287 Q2. When to specify REQ_IDLE
290 to specify REQ_IDLE on writes and that probably should work well for
/Linux-v4.19/include/linux/
Dblk_types.h341 #define REQ_IDLE (1ULL << __REQ_IDLE) macro
/Linux-v4.19/block/
Dblk-wbt.c584 if ((bio->bi_opf & (REQ_SYNC | REQ_IDLE)) == in wbt_should_throttle()
585 (REQ_SYNC | REQ_IDLE)) in wbt_should_throttle()
Dcfq-iosched.c3914 (req->cmd_flags & (REQ_SYNC | REQ_IDLE)) == REQ_SYNC; in req_noidle()
/Linux-v4.19/drivers/nvme/target/
Dio-cmd-bdev.c74 op_flags = REQ_SYNC | REQ_IDLE; in nvmet_bdev_execute_rw()
/Linux-v4.19/fs/
Diomap.c1567 bio_set_op_attrs(bio, REQ_OP_WRITE, REQ_SYNC | REQ_IDLE); in iomap_dio_zero()
1654 bio->bi_opf = REQ_OP_WRITE | REQ_SYNC | REQ_IDLE; in iomap_dio_bio_actor()
Ddirect-io.c1262 dio->op_flags = REQ_SYNC | REQ_IDLE; in do_blockdev_direct_IO()
Dblock_dev.c169 unsigned int op = REQ_OP_WRITE | REQ_SYNC | REQ_IDLE; in dio_bio_write_op()
/Linux-v4.19/drivers/block/xen-blkback/
Dblkback.c1257 operation_flags = REQ_SYNC | REQ_IDLE; in dispatch_rw_block_io()