From: Miroslav Lichvar <mlichvar@redhat.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Jacob Keller <jacob.e.keller@intel.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next v2] igb: Convert Tx timestamping to PTP aux worker
Date: Mon, 25 Aug 2025 09:53:44 +0200 [thread overview]
Message-ID: <aKwWiGkbDyEOS9-z@localhost> (raw)
In-Reply-To: <87ldna7axr.fsf@jax.kurt.home>
On Sat, Aug 23, 2025 at 09:29:36AM +0200, Kurt Kanzenbach wrote:
> Also I couldn't really see a performance degradation with ntpperf.
I was testing with an I350, not I210. Could that make a difference?
> In my
> tests the IRQ variant reached an equal or higher rate. But sometimes I
> get 'Could not send requests at rate X'. No idea what that means.
That's ntpperf giving up as the HW is too slow to send requests at
that rate (with a single process calling sendmmsg() in a loop). You
can add the -l option to force ntpperf to continue, but the printed
rate values will no longer be accurate, you would need to measure it
by some other way, e.g. by monitoring the interface packet counters.
--
Miroslav Lichvar
next prev parent reply other threads:[~2025-08-25 7:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:28 [PATCH iwl-next v2] igb: Convert Tx timestamping to PTP aux worker Kurt Kanzenbach
2025-08-22 7:52 ` Sebastian Andrzej Siewior
2025-08-22 23:55 ` Jacob Keller
2025-08-23 7:29 ` Kurt Kanzenbach
2025-08-25 7:53 ` Miroslav Lichvar [this message]
2025-08-25 9:22 ` Kurt Kanzenbach
2025-08-25 23:23 ` [Intel-wired-lan] " Jacob Keller
2025-08-25 23:28 ` Jacob Keller
2025-08-26 12:59 ` Sebastian Andrzej Siewior
2025-08-26 18:23 ` Jacob Keller
2025-08-27 12:57 ` Kurt Kanzenbach
2025-08-27 13:39 ` Paul Menzel
2025-08-27 16:22 ` Jacob Keller
2025-08-27 13:57 ` Miroslav Lichvar
2025-08-27 14:05 ` Kurt Kanzenbach
2025-08-27 14:10 ` Sebastian Andrzej Siewior
2025-08-27 14:41 ` Miroslav Lichvar
2025-08-27 14:52 ` Sebastian Andrzej Siewior
2025-08-27 16:21 ` Jacob Keller
2025-08-22 16:27 ` Vadim Fedorenko
2025-08-23 7:44 ` Kurt Kanzenbach
2025-08-25 13:18 ` Vadim Fedorenko
2025-08-25 23:24 ` Jacob Keller
2025-08-25 10:58 ` [Intel-wired-lan] " Loktionov, Aleksandr
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=aKwWiGkbDyEOS9-z@localhost \
--to=mlichvar@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vinicius.gomes@intel.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