summaryrefslogtreecommitdiffstats
path: root/fs/sync.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2013-06-21 08:58:18 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2013-06-29 12:57:44 +0400
commit48f74186546cd5929397856eab209ebcb5692d11 (patch)
tree9a4bf88cd5171f470eeae0ba4f62d5b5b9d06fc7 /fs/sync.c
parent139ca04ee572fea6c0c105e88aba3a534efcd7c4 (diff)
downloadlinux-stable-48f74186546cd5929397856eab209ebcb5692d11.tar.gz
linux-stable-48f74186546cd5929397856eab209ebcb5692d11.tar.bz2
linux-stable-48f74186546cd5929397856eab209ebcb5692d11.zip
locks: turn the blocked_list into a hashtable
Break up the blocked_list into a hashtable, using the fl_owner as a key. This speeds up searching the hash chains, which is especially significant for deadlock detection. Note that the initial implementation assumes that hashing on fl_owner is sufficient. In most cases it should be, with the notable exception being server-side lockd, which compares ownership using a tuple of the nlm_host and the pid sent in the lock request. So, this may degrade to a single hash bucket when you only have a single NFS client. That will be addressed in a later patch. The careful observer may note that this patch leaves the file_lock_list alone. There's much less of a case for turning the file_lock_list into a hashtable. The only user of that list is the code that generates /proc/locks, and it always walks the entire list. Signed-off-by: Jeff Layton <jlayton@redhat.com> Acked-by: J. Bruce Fields <bfields@fieldses.org> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/sync.c')
0 files changed, 0 insertions, 0 deletions