diff options
author | Jeff Layton | 2012-03-21 14:52:02 +0100 |
---|---|---|
committer | J. Bruce Fields | 2012-03-26 17:49:47 +0200 |
commit | a52d726bbd928164609e6abc4dc967e819dbf09c (patch) | |
tree | 604df65589a95311ab297f80ce377e82525ce597 /net/sunrpc/rpc_pipe.c | |
parent | Merge nfs containerization work from Trond's tree (diff) | |
download | kernel-qcow2-linux-a52d726bbd928164609e6abc4dc967e819dbf09c.tar.gz kernel-qcow2-linux-a52d726bbd928164609e6abc4dc967e819dbf09c.tar.xz kernel-qcow2-linux-a52d726bbd928164609e6abc4dc967e819dbf09c.zip |
nfsd: convert nfs4_client->cl_cb_flags to a generic flags field
We'll need a way to flag the nfs4_client as already being recorded on
stable storage so that we don't continually upcall. Currently, that's
recorded in the cl_firststate field of the client struct. Using an
entire u32 to store a flag is rather wasteful though.
The cl_cb_flags field is only using 2 bits right now, so repurpose that
to a generic flags field. Rename NFSD4_CLIENT_KILL to
NFSD4_CLIENT_CB_KILL to make it evident that it's part of the callback
flags. Add a mask that we can use for existing checks that look to see
whether any flags are set, so that the new flags don't interfere.
Convert all references to cl_firstate to the NFSD4_CLIENT_STABLE flag,
and add a new NFSD4_CLIENT_RECLAIM_COMPLETE flag.
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'net/sunrpc/rpc_pipe.c')
0 files changed, 0 insertions, 0 deletions