• J
    locks: add a new "lm_owner_key" lock operation · 3999e493
    Jeff Layton 提交于
    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: NJeff Layton <jlayton@redhat.com>
    Acked-by: NJ. Bruce Fields <bfields@fieldses.org>
    Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
    3999e493
fs.h 90.5 KB