summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorZhe Liu <liuzhe1@kylinos.cn>2026-08-10 14:35:35 +0800
committerTejun Heo <tj@kernel.org>2026-08-10 09:34:22 -1000
commit3345c7248a9e2a91cb9e2477c29af16881706f4f (patch)
tree6cfa0f18aeeee40ca6afcbee15f6cec5bbe42894 /tools/perf/scripts/python/stackcollapse.py
parent75e79a20190040800445ec95a4c4a84193d16992 (diff)
docs: cgroup-v2: fix stale "io" controller introduction
The introductory paragraph for the IO controller still states that weight based distribution is "available only if cfq-iosched is in use" and that "neither scheme is available for blk-mq devices". This text dates from when the cgroup v2 documentation was first written (2015) and was correct at the time, but is no longer accurate: * cfq-iosched was removed in v5.0; * blk-mq is now the only block I/O path, and both the absolute limit scheme (io.max via blk-throttle) and the weight based scheme (io.weight via iocost, or io.bfq.weight under BFQ) work on it; * latency based protection (iolatency) and I/O priority (ioprio) controllers have since been added. The rest of the section already documents io.weight, io.max, io.cost.{qos,model}, io.latency and io.prio.class correctly, so the introduction is the only part that contradicts them. Rewrite it to reflect the current state. Signed-off-by: Zhe Liu <liuzhe1@kylinos.cn> Reviewed-by: Tao Cui <cuitao@kylinos.cn> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions