[PATCH v2] fs: nfs: Start earlier to resend requests
Sascha Hauer
sha at pengutronix.de
Fri Jun 11 04:13:57 PDT 2021
On Fri, Jun 11, 2021 at 09:13:51AM +0200, Uwe Kleine-König wrote:
> On a customer site we're experience a bit over 1% UDP packet loss. When
> wiresharking an NFS transfer of a kernel image (with the goal to boot
> via NFS) I saw 64 of 2555 RPC calls staying unanswered. With the current
> timeout setting each of them introduces a delay of 2 seconds and the
> whole transfer takes 137s. With the timeout reduced to 0.1s the transfer
> time is not optimal (going down to approx 15 seconds) but at least it
> becomes bearable.
>
> To still cope with a slow network (in contrast to an unreliable as
> pictured above) increase NFS_MAX_RESEND to keep NFS_TIMEOUT *
> NFS_MAX_RESEND (which defines the overall timeout before aborting the
> transfer) constant.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig at pengutronix.de>
> ---
> fs/nfs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list