diff options
author | Boaz Harrosh <bharrosh@panasas.com> | 2014-01-22 20:34:54 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-02-13 13:48:01 -0800 |
commit | 305a7c624df026dbdde23eb880549db7df0ad7b9 (patch) | |
tree | ae7c38a79a1b5e61d64d6bcba0626ad18354e1e9 /net/sunrpc/clnt.c | |
parent | daab6e7df44ba7d4281379c6ac5780e10d133286 (diff) | |
download | linux-3.10-305a7c624df026dbdde23eb880549db7df0ad7b9.tar.gz linux-3.10-305a7c624df026dbdde23eb880549db7df0ad7b9.tar.bz2 linux-3.10-305a7c624df026dbdde23eb880549db7df0ad7b9.zip |
pnfs: Proper delay for NFS4ERR_RECALLCONFLICT in layout_get_done
commit ed7e5423014ad89720fcf315c0b73f2c5d0c7bd2 upstream.
An NFS4ERR_RECALLCONFLICT is returned by server from a GET_LAYOUT
only when a Server Sent a RECALL do to that GET_LAYOUT, or
the RECALL and GET_LAYOUT crossed on the wire.
In any way this means we want to wait at most until in-flight IO
is finished and the RECALL can be satisfied.
So a proper wait here is more like 1/10 of a second, not 15 seconds
like we have now. In case of a server bug we delay exponentially
longer on each retry.
Current code totally craps out performance of very large files on
most pnfs-objects layouts, because of how the map changes when the
file has grown into the next raid group.
[Stable: This will patch back to 3.9. If there are earlier still
maintained trees, please tell me I'll send a patch]
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/sunrpc/clnt.c')
0 files changed, 0 insertions, 0 deletions