summaryrefslogtreecommitdiffstats
path: root/net/llc/llc_proc.c
diff options
context:
space:
mode:
authorJeff Layton2012-11-12 21:00:55 +0100
committerJ. Bruce Fields2012-11-13 00:55:11 +0100
commit0ce0c2b5d23080eec39ccc52354be1eea326ed5f (patch)
tree560db260bfd579a0b78f75eca46fbf67a90ed6ed /net/llc/llc_proc.c
parentnfsd: make nfs4_client_to_reclaim return a pointer to the reclaim record (diff)
downloadkernel-qcow2-linux-0ce0c2b5d23080eec39ccc52354be1eea326ed5f.tar.gz
kernel-qcow2-linux-0ce0c2b5d23080eec39ccc52354be1eea326ed5f.tar.xz
kernel-qcow2-linux-0ce0c2b5d23080eec39ccc52354be1eea326ed5f.zip
nfsd: don't search for client by hash on legacy reboot recovery gracedone
When nfsd starts, the legacy reboot recovery code creates a tracking struct for each directory in the v4recoverydir. When the grace period ends, it basically does a "readdir" on the directory again, and matches each dentry in there to an existing client id to see if it should be removed or not. If the matching client doesn't exist, or hasn't reclaimed its state then it will remove that dentry. This is pretty inefficient since it involves doing a lot of hash-bucket searching. It also means that we have to keep relying on being able to search for a nfs4_client by md5 hashed cl_recdir name. Instead, add a pointer to the nfs4_client that indicates the association between the nfs4_client_reclaim and nfs4_client. When a reclaim operation comes in, we set the pointer to make that association. On gracedone, the legacy client tracker will keep the recdir around iff: 1/ there is a reclaim record for the directory ...and... 2/ there's an association between the reclaim record and a client record -- that is, a create or check operation was performed on the client that matches that directory. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'net/llc/llc_proc.c')
0 files changed, 0 insertions, 0 deletions