From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, Petr Machata <petrm@nvidia.com>
Subject: Re: [PATCH net-next 1/2] selftests: drv-net: pace ethtool_std_stats packet generation
Date: Tue, 11 Aug 2026 09:23:52 +0200 [thread overview]
Message-ID: <8733wl86if.fsf@pmachata.org> (raw)
In-Reply-To: <20260810164858.7fdd834a@kernel.org> (Jakub Kicinski's message of "Mon, 10 Aug 2026 16:48:58 -0700")
Jakub Kicinski <kuba@kernel.org> writes:
> On Mon, 10 Aug 2026 11:48:32 +0200 Petr Machata wrote:
>> Jakub Kicinski <kuba@kernel.org> writes:
>> > 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>
>>
>> Reviewed-by: Petr Machata <petrm@nvidia.com>
>
> FTR Petr send me a review tag on this off-list ;)
Oops, that was not the intention.
My mailer setup is currently in a bit of a flux :-|
next prev parent reply other threads:[~2026-08-11 7:39 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 [this message]
2026-08-11 0:00 ` patchwork-bot+netdevbpf
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=8733wl86if.fsf@pmachata.org \
--to=petrm@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox