aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-sql.py
diff options
context:
space:
mode:
authorLiu Bo <[email protected]>2018-05-18 11:00:23 +0800
committerDavid Sterba <[email protected]>2018-05-30 16:46:51 +0200
commit662c653bfda58698cf48d7143a39bd3a063fd9c6 (patch)
treec4996ca4d8c9fd5410c400dfdffaa1dadddb2cc6 /tools/perf/scripts/python/call-graph-from-sql.py
parent1fc28d8e2e9bf22044f1bacd17fe941cd0df5ba6 (diff)
Btrfs: grab write lock directly if write_lock_level is the max level
Typically, when acquiring root node's lock, btrfs tries its best to get read lock and trade for write lock if @write_lock_level implies to do so. In case of (cow && (p->keep_locks || p->lowest_level)), write_lock_level is set to BTRFS_MAX_LEVEL, which means we need to acquire root node's write lock directly. In this particular case, the dance of acquiring read lock and then trading for write lock can be saved. Signed-off-by: Liu Bo <[email protected]> Reviewed-by: David Sterba <[email protected]> Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions