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, andrew+netdev@lunn.ch, horms@kernel.org,
andrew@lunn.ch, shuah@kernel.org, petrm@nvidia.com,
ioana.ciornei@nxp.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] selftests: drv-net: pace ethtool_std_stats packet generation
Date: Tue, 11 Aug 2026 00:00:08 +0000 [thread overview]
Message-ID: <178640640814.260499.16695015712060305281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808163653.2460381-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 8 Aug 2026 09:36:52 -0700 you wrote:
> mausezahn defaults to sending packets back to back at the maximum rate,
> which can cause packet loss, especially if receiver is running a debug
> kernel. Space the generated packets out (-d 10usec), like ethtool_rmon
> already does.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: drv-net: pace ethtool_std_stats packet generation
https://git.kernel.org/netdev/net-next/c/f4cf60568747
- [net-next,2/2] selftests: drv-net: let ethtool stats settle before reading
https://git.kernel.org/netdev/net-next/c/855631afe0f5
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:[~2026-08-11 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 16:36 [PATCH net-next 1/2] selftests: drv-net: pace ethtool_std_stats packet generation Jakub Kicinski
2026-08-08 16:36 ` [PATCH net-next 2/2] selftests: drv-net: let ethtool stats settle before reading Jakub Kicinski
2026-08-08 16:52 ` Andrew Lunn
[not found] ` <87ecg6cnm7.fsf@pmachata.org>
2026-08-10 23:48 ` [PATCH net-next 1/2] selftests: drv-net: pace ethtool_std_stats packet generation Jakub Kicinski
2026-08-11 7:23 ` Petr Machata
2026-08-11 0: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=178640640814.260499.16695015712060305281.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.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.