aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2024-04-20 17:40:47 -0400
committerKent Overstreet <kent.overstreet@linux.dev>2025-05-21 20:14:23 -0400
commit9e260e4590e044dc5887f9eb21dfaf479226e7d4 (patch)
treef755ad51bdc1e47c3474e6c6bd86ddcd409fb474 /tools/perf/scripts/python/bin/stackcollapse-record
parentbcachefs: bch2_move_data_btree() can now walk roots (diff)
downloadlinux-9e260e4590e044dc5887f9eb21dfaf479226e7d4.tar.gz
linux-9e260e4590e044dc5887f9eb21dfaf479226e7d4.zip
docs: bcachefs: idle work scheduling design doc
People have been asking to see the plan for this, so - bcachefs has various background tasks that need to be scheduled to balance efficiency, predictability of performance, etc. The design and philosophy hasn't changed too much since bcache, which was primarily designed for server usage, with sustained load in mind. These days we're seeing more desktop usage - where we really want to let the system idle effictively, to reduce total power usage - while also still balancing previous concerns, we still want to let work accumulate to a degree. This lays out all the requirements and starts to sketch out the algorithm I have in mind. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions