mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Gavin Schenk <g.schenk@eckelmann.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] fs: nfs: Start earlier to resend requests
Date: Fri, 11 Jun 2021 10:52:26 +0200	[thread overview]
Message-ID: <20210611085226.5hzbvsbz2m6gcxle@NB061.eckelmann.group> (raw)
In-Reply-To: <20210611071351.1445370-1-u.kleine-koenig@pengutronix.de>

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@pengutronix.de>
Acked-by: Gavin Schenk <g.schenk@eckelmann.de>

I have tested this on the customer site with 1% UDP loss :). I am working with
the IT department to get a better network. Until that happens, this patch helps
me successfully boot NFS.

Regards
Gavin Schenk

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2021-06-11  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  7:13 Uwe Kleine-König
2021-06-11  8:52 ` Gavin Schenk [this message]
2021-06-11 11:13 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210611085226.5hzbvsbz2m6gcxle@NB061.eckelmann.group \
    --to=g.schenk@eckelmann.de \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox