16 Dec, 2012
2 commits
-
If an RPC call is interrupted, assume that the server hasn't processed
the RPC call so that the next time we use the slot, we know that if we
get a NFS4ERR_SEQ_MISORDERED or NFS4ERR_SEQ_FALSE_RETRY, we just have
to bump the sequence number.Signed-off-by: Trond Myklebust
-
Shave a few bytes off the slot table size by moving the RPC timestamp
into the sequence results.Signed-off-by: Trond Myklebust
12 Dec, 2012
1 commit
-
If the server sends us a target that looks like an outlier, but
is lower than the existing target, then respect it anyway.
However defer actually updating the generation counter until
we get a target that doesn't look like an outlier.Signed-off-by: Trond Myklebust
06 Dec, 2012
3 commits
-
Look for sudden changes in the first and second derivatives in order
to eliminate outlier changes to target_highest_slotid (which are
due to out-of-order RPC replies).Signed-off-by: Trond Myklebust
-
Currently, we see a lot of bouncing for the value of highest_used_slotid
due to the fact that slots are getting freed, instead of getting instantly
transmitted to the next waiting task.Signed-off-by: Trond Myklebust
-
NFSv4.1 session management is getting complex enough to deserve
a separate file.Signed-off-by: Trond Myklebust