netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: Petr Machata <petrm@nvidia.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] gre_multipath_nh_res takes forever
Date: Mon, 19 Feb 2024 11:17:21 -0800	[thread overview]
Message-ID: <20240219111721.2f97be53@kernel.org> (raw)
In-Reply-To: <ZdOG8oxNu5gOImDd@shredder>

On Mon, 19 Feb 2024 18:50:58 +0200 Ido Schimmel wrote:
> > I bumped the timeouts for forwarding tests with kernel debug enabled
> > yesterday, and gre_multipath_nh_res still doesn't finish even tho it
> > runs for close to 3 hours. On a non-debug kernel it takes around 30min.
> > 
> > You probably have a better idea how to address this than me, but it
> > seems to time out on the IPv6 tests - I wonder if using mausezahn 
> > instead of ping for IPv6 would help a bit?  
> 
> Converted from ping6 to mausezahn, but the test was still relatively
> slow because of the 1msec delay we pass the mausezahn. After converting
> to mausezahn and removing the delay the runtime dropped from ~350
> seconds to ~15 seconds on my system.

Great!

> I think I will parametrize the delay for platforms that might need it,
> but default it to 0 as it's not needed with veth. The same change is
> needed in other tests. Will submit it together with Petr's selftest
> changes.

SG, thanks!

      reply	other threads:[~2024-02-19 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 17:50 [TEST] gre_multipath_nh_res takes forever Jakub Kicinski
2024-02-19 16:50 ` Ido Schimmel
2024-02-19 19:17   ` 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=20240219111721.2f97be53@kernel.org \
    --to=kuba@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).