diff options
| author | Ilya Dryomov <idryomov@gmail.com> | 2017-04-13 06:17:39 -0400 |
|---|---|---|
| committer | Ilya Dryomov <idryomov@gmail.com> | 2017-05-04 03:19:23 -0400 |
| commit | f9bebd580360c141b5fdbede9cc13a4caf23cd1a (patch) | |
| tree | ab3d7c8f24c84001554e6159e7eb00b1e24e62d3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 14bb211d324d6c8140167bd6b2b8a80757348a2f (diff) | |
rbd: kill rbd_is_lock_supported()
Currently the exclusive lock is acquired only if the mapping is
writable, i.e. an image HEAD mapped in rw mode. This means that we
don't acquire the lock for executing a read from a snapshot or an image
HEAD mapped in ro mode, even if lock_on_read is set. This is somewhat
weird and inconsistent with "no automatic exclusive lock transfers"
mode, where the lock is acquired unconditionally.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Reviewed-by: Jason Dillaman <dillaman@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions