mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-11-01 08:58:07 +00:00
btrfs: avoid pointless wake ups of drew lock readers
When unlocking a write lock on a drew lock, at btrfs_drew_write_unlock(), it's pointless to wake up tasks waiting to acquire a read lock if we didn't decrement the 'writers' counter down to 0, since a read lock can only be acquired when the counter reaches a value of 0. Doing so is harmless from a functional point of view, but it's not efficient due to unnecessarily waking up tasks just for them to sleep again on the waitqueue. So change this to wake up readers only if we decremented the 'writers' counter to 0. Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
c66f2afc71
commit
c79f57eafc
1 changed files with 6 additions and 2 deletions
|
@ -364,8 +364,12 @@ void btrfs_drew_write_lock(struct btrfs_drew_lock *lock)
|
|||
|
||||
void btrfs_drew_write_unlock(struct btrfs_drew_lock *lock)
|
||||
{
|
||||
atomic_dec(&lock->writers);
|
||||
cond_wake_up(&lock->pending_readers);
|
||||
/*
|
||||
* atomic_dec_and_test() implies a full barrier, so woken up readers are
|
||||
* guaranteed to see the decrement.
|
||||
*/
|
||||
if (atomic_dec_and_test(&lock->writers))
|
||||
wake_up(&lock->pending_readers);
|
||||
}
|
||||
|
||||
void btrfs_drew_read_lock(struct btrfs_drew_lock *lock)
|
||||
|
|
Loading…
Reference in a new issue