Home
last modified time | relevance | path

Searched refs:slice_idle (Results 1 – 3 of 3) sorted by relevance

/linux-4.4.14/Documentation/block/
Dcfq-iosched.txt15 slice_idle
21 By default slice_idle is a non-zero value. That means by default we idle on
26 Setting slice_idle to 0 will remove all the idling on queues/service tree
32 So depending on storage and workload, it might be useful to set slice_idle=0.
34 keeping slice_idle enabled should be useful. For any configurations where
36 controller or for storage arrays), setting slice_idle=0 might end up in better
75 slice_idle=0 and group_idle=8, so that idling does not happen on individual
218 If one sets slice_idle=0 and if storage supports NCQ, CFQ internally switches
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt351 /sys/block/<disk>/queue/iosched/slice_idle
356 one can try setting slice_idle=0 and that would switch CFQ to IOPS
367 setting slice_idle=0, group_idle kicks in. That means CFQ will still idle
370 By default group_idle is same as slice_idle and does not do anything if
371 slice_idle is enabled.
/linux-4.4.14/block/
Dcfq-iosched.c3830 __cfq_update_io_thinktime(struct cfq_ttime *ttime, unsigned long slice_idle) in __cfq_update_io_thinktime() argument
3833 elapsed = min(elapsed, 2UL * slice_idle); in __cfq_update_io_thinktime()
4697 CFQ_ATTR(slice_idle),