commit | 7b2296afb392bc21a50f42e7c7f4b19d3fea8c6d | [log] [tgz] |
---|---|---|
author | Jeff Layton <jlayton@redhat.com> | Fri Jun 21 08:58:20 2013 -0400 |
committer | Al Viro <viro@zeniv.linux.org.uk> | Sat Jun 29 12:57:46 2013 +0400 |
tree | 360a8f35cf75f0bbcd1b984a6348f4c9e715e159 | |
parent | 3999e49364193f7dbbba66e2be655fe91ba1fced [diff] |
locks: give the blocked_hash its own spinlock There's no reason we have to protect the blocked_hash and file_lock_list with the same spinlock. With the tests I have, breaking it in two gives a barely measurable performance benefit, but it seems reasonable to make this locking as granular as possible. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>