diff options
author | 2019-10-27 15:01:43 -0700 | |
---|---|---|
committer | 2019-11-18 14:26:43 +0100 | |
commit | 6060c07d476ebb1f21d28db5ba852e911246ce79 (patch) | |
tree | e72425a98d8915b3209e3136b1e4b575c009794a /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Linux 5.4-rc8 (diff) | |
download | linux-rng-6060c07d476ebb1f21d28db5ba852e911246ce79.tar.xz linux-rng-6060c07d476ebb1f21d28db5ba852e911246ce79.zip |
affs: Replace binary semaphores with mutexes
At a slight footprint cost (24 vs 32 bytes), mutexes are more optimal
than semaphores; it's also a nicer interface for mutual exclusion,
which is why they are encouraged over binary semaphores, when possible.
For both i_link_lock and i_ext_lock (and hence i_hash_lock which I
annotated for the hash lock mapping hackery for lockdep), their semantics
imply traditional lock ownership; that is, the lock owner is the same for
both lock/unlock operations and does not run in irq context. Therefore
it is safe to convert.
Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions