summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorKent Overstreet <kent.overstreet@linux.dev>2025-04-13 06:44:23 -0400
committerKent Overstreet <kent.overstreet@linux.dev>2025-04-21 11:57:24 -0400
commit387df331298eaa9d6dbb4e30f376d632dd798b46 (patch)
treec69ffcbc13602b414c87466e71cf293141e83c06 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentd64e8e842bb18403d03a85b29caa5cb5f3bd4c7d (diff)
bcachefs: Start copygc, rebalance threads earlier
Previously, copygc and rebalance weren't started until the very end of mounting, after all recvoery passes have finished. But copygc really should be started earlier, since it may be needed for allocations to make forward progress. Additionally, we've been seeing occasional bug reports where starting the kthread fails due to a pending signal - i.e. we're getting timed out by systemd (during a version upgrade), but we're not seeing the signal until mount is about to complete. Additionally, we now have copygc/rebalance explicitly wait for check_snapshots to complete (if being run); they require that for snapshot_is_ancestor() in the data move path. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions