All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	Willem de Bruijn <willemb@google.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH net-next] selftests/net: make so_txtime more robust to timer variance
Date: Sat, 14 Dec 2019 18:05:09 -0800	[thread overview]
Message-ID: <20191214180509.2dfd117d@cakuba.netronome.com> (raw)
In-Reply-To: <20191212163646.190982-1-willemdebruijn.kernel@gmail.com>

On Thu, 12 Dec 2019 11:36:46 -0500, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> The SO_TXTIME test depends on accurate timers. In some virtualized
> environments the test has been reported to be flaky. This is easily
> reproduced by disabling kvm acceleration in Qemu.
> 
> Allow greater variance in a run and retry to further reduce flakiness.
> 
> Observed errors are one of two kinds: either the packet arrives too
> early or late at recv(), or it was dropped in the qdisc itself and the
> recv() call times out.
> 
> In the latter case, the qdisc queues a notification to the error
> queue of the send socket. Also explicitly report this cause.
> 
> Link: https://lore.kernel.org/netdev/CA+FuTSdYOnJCsGuj43xwV1jxvYsaoa_LzHQF9qMyhrkLrivxKw@mail.gmail.com
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Signed-off-by: Willem de Bruijn <willemb@google.com>

Applied, thank you!

      reply	other threads:[~2019-12-15  2:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 16:36 [PATCH net-next] selftests/net: make so_txtime more robust to timer variance Willem de Bruijn
2019-12-15  2:05 ` Jakub Kicinski [this message]

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=20191214180509.2dfd117d@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=davem@davemloft.net \
    --cc=naresh.kamboju@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.