From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, dw@davidwei.uk, petrm@nvidia.com,
willemb@google.com
Subject: Re: [PATCH net-next] selftests: drv-net: rss_ctx: allow more noise on default context
Date: Thu, 04 Jul 2024 02:30:28 +0000 [thread overview]
Message-ID: <172006022854.6400.9654309823031582639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240702233728.4183387-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 2 Jul 2024 16:37:28 -0700 you wrote:
> As predicted by David running the test on a machine with a single
> interface is a bit unreliable. We try to send 20k packets with
> iperf and expect fewer than 10k packets on the default context.
> The test isn't very quick, iperf will usually send 100k packets
> by the time we stop it. So we're off by 5x on the number of iperf
> packets but still expect default context to only get the hardcoded
> 10k. The intent is to make sure we get noticeably less traffic
> on the default context. Use half of the resulting iperf traffic
> instead of the hard coded 10k.
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: rss_ctx: allow more noise on default context
https://git.kernel.org/netdev/net-next/c/0b8774586be5
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:[~2024-07-04 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 23:37 [PATCH net-next] selftests: drv-net: rss_ctx: allow more noise on default context Jakub Kicinski
2024-07-04 2:30 ` 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=172006022854.6400.9654309823031582639.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--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 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).