| commit | ecdd03b7914c91ef849e49c4d466c87f4981b5cd | |
| author | J. Bruce Fields <bfields@citi.umich.edu> | |
| Tue, 24 Feb 2009 03:35:22 +0000 (23 19:35 -0800) | ||
| committer | J. Bruce Fields <bfields@citi.umich.edu> | |
| Wed, 29 Apr 2009 20:44:53 +0000 (29 16:44 -0400) | ||
| tree | 16d67b4af0e8545f60e31f0b1f9cfb0f97526641 | treesnapshot (tar.gz zip) |
| parent | e1cab5a5896e142190cd66a8287099b52e5855a7 | commitdiff |
nfsd4: create rpc callback client from server thread
The code is a little simpler, and it should be easier to avoid races, if
we just do all rpc client creation/destruction from nfsd or laundromat
threads and do only the rpc calls themselves asynchronously. The rpc
creation doesn't involve any significant waiting (it doesn't call the
client, for example), so there's no reason not to do this.
Also don't bother destroying the client on failure of the rpc null
probe. We may want to retry the probe later anyway.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
The code is a little simpler, and it should be easier to avoid races, if
we just do all rpc client creation/destruction from nfsd or laundromat
threads and do only the rpc calls themselves asynchronously. The rpc
creation doesn't involve any significant waiting (it doesn't call the
client, for example), so there's no reason not to do this.
Also don't bother destroying the client on failure of the rpc null
probe. We may want to retry the probe later anyway.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
| fs/nfsd/nfs4callback.c | diffblobblamehistory |