[PATCH v2] fs: nfs: Start earlier to resend requests

Uwe Kleine-König u.kleine-koenig at pengutronix.de
Fri Jun 11 00:13:51 PDT 2021

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(-)

diff --git a/fs/nfs.c b/fs/nfs.c
index 1130632eb3eb..057641edc8c3 100644
--- a/fs/nfs.c
+++ b/fs/nfs.c
@@ -119,8 +119,8 @@ struct rpc_reply {
 	uint32_t data[0];
-#define NFS_TIMEOUT	(2 * SECOND)
-#define NFS_MAX_RESEND	5
+#define NFS_TIMEOUT	(100 * MSECOND)
+#define NFS_MAX_RESEND	100
 struct nfs_fh {
 	unsigned short size;

More information about the barebox mailing list