From: patchwork-bot+netdevbpf@kernel.org
To: Nimrod Oren <noren@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
willemb@google.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, gal@nvidia.com,
cjubran@nvidia.com
Subject: Re: [PATCH net v2] selftests: drv-net: wait for iperf client to stop sending
Date: Thu, 24 Jul 2025 02:00:06 +0000 [thread overview]
Message-ID: <175332240625.1844642.3670476932711392299.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250722122655.3194442-1-noren@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Jul 2025 15:26:55 +0300 you wrote:
> A few packets may still be sent out during the termination of iperf
> processes. These late packets cause failures in rss_ctx.py when they
> arrive on queues expected to be empty.
>
> Example failure observed:
>
> Check failed 2 != 0 traffic on inactive queues (context 1):
> [0, 0, 1, 1, 386385, 397196, 0, 0, 0, 0, ...]
>
> [...]
Here is the summary with links:
- [net,v2] selftests: drv-net: wait for iperf client to stop sending
https://git.kernel.org/netdev/net/c/869413825088
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-07-24 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 12:26 [PATCH net v2] selftests: drv-net: wait for iperf client to stop sending Nimrod Oren
2025-07-23 15:37 ` Simon Horman
2025-07-24 2:00 ` 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=175332240625.1844642.3670476932711392299.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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.