All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, petrm@nvidia.com,
	bpoirier@nvidia.com, shuah@kernel.org
Subject: Re: [PATCH net-next 0/6] selftests: forwarding: Various improvements
Date: Tue, 05 Mar 2024 18:40:35 +0000	[thread overview]
Message-ID: <170966403546.3255.13508375715616168106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304095612.462900-1-idosch@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 4 Mar 2024 11:56:06 +0200 you wrote:
> This patchset speeds up the multipath tests (patches #1-#2) and makes
> other tests more stable (patches #3-#6) so that they will not randomly
> fail in the netdev CI.
> 
> On my system, after applying the first two patches, the run time of
> gre_multipath_nh_res.sh is reduced by over 90%.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] selftests: forwarding: Remove IPv6 L3 multipath hash tests
    https://git.kernel.org/netdev/net-next/c/7b2d64f93319
  - [net-next,2/6] selftests: forwarding: Parametrize mausezahn delay
    https://git.kernel.org/netdev/net-next/c/748d27447daa
  - [net-next,3/6] selftests: forwarding: Make tc-police pass on debug kernels
    https://git.kernel.org/netdev/net-next/c/4aca9eae6f7b
  - [net-next,4/6] selftests: forwarding: Make vxlan-bridge-1q pass on debug kernels
    https://git.kernel.org/netdev/net-next/c/dfbab74044be
  - [net-next,5/6] selftests: forwarding: Make VXLAN ECN encap tests more robust
    https://git.kernel.org/netdev/net-next/c/f0008b04977a
  - [net-next,6/6] selftests: forwarding: Make {, ip6}gre-inner-v6-multipath tests more robust
    https://git.kernel.org/netdev/net-next/c/35df2ce896dc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-03-05 18:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04  9:56 [PATCH net-next 0/6] selftests: forwarding: Various improvements Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 1/6] selftests: forwarding: Remove IPv6 L3 multipath hash tests Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 2/6] selftests: forwarding: Parametrize mausezahn delay Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 3/6] selftests: forwarding: Make tc-police pass on debug kernels Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 4/6] selftests: forwarding: Make vxlan-bridge-1q " Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 5/6] selftests: forwarding: Make VXLAN ECN encap tests more robust Ido Schimmel
2024-03-04  9:56 ` [PATCH net-next 6/6] selftests: forwarding: Make {, ip6}gre-inner-v6-multipath " Ido Schimmel
2024-03-04 14:43 ` [PATCH net-next 0/6] selftests: forwarding: Various improvements Jakub Kicinski
2024-03-05 18:40 ` patchwork-bot+netdevbpf [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=170966403546.3255.13508375715616168106.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpoirier@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=shuah@kernel.org \
    /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.