Jeff Layton 3999e49364 locks: add a new "lm_owner_key" lock operation ... Currently, the hashing that the locking code uses to add these values to the blocked_hash is simply calculated using fl_owner field. That's valid in most cases except for server-side lockd, which validates the owner of a lock based on fl_owner and fl_pid. In the case where you have a small number of NFS clients doing a lot of locking between different processes, you could end up with all the blocked requests sitting in a very small number of hash buckets. Add a new lm_owner_key operation to the lock_manager_operations that will generate an unsigned long to use as the key in the hashtable. That function is only implemented for server-side lockd, and simply XORs the fl_owner and fl_pid. 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>		2013-06-29 12:57:45 +04:00
..
clnt4xdr.c
clntlock.c	LOCKD: Ensure that nlmclnt_block resets block->b_status after a server reboot	2013-04-21 18:08:42 -04:00
clntproc.c	LOCKD: Ensure that nlmclnt_block resets block->b_status after a server reboot	2013-04-21 18:08:42 -04:00
clntxdr.c
grace.c
host.c
Makefile
mon.c
netns.h
svc4proc.c
svc.c
svclock.c	locks: add a new "lm_owner_key" lock operation	2013-06-29 12:57:45 +04:00
svcproc.c
svcshare.c
svcsubs.c	locks: protect most of the file_lock handling with i_lock	2013-06-29 12:57:42 +04:00
xdr4.c
xdr.c