On Mon Aug 18 2025, Miroslav Lichvar wrote: > On Fri, Aug 15, 2025 at 08:50:23AM +0200, Kurt Kanzenbach wrote: >> Retrieve Tx timestamp directly from interrupt handler. >> >> The current implementation uses schedule_work() which is executed by the >> system work queue to retrieve Tx timestamps. This increases latency and can >> lead to timeouts in case of heavy system load. >> >> Therefore, fetch the timestamp directly from the interrupt handler. >> >> The work queue code stays for the Intel 82576. Tested on Intel i210. > > I tested this patch on 6.17-rc1 with an Intel I350 card on a NTP > server (chrony 4.4), measuring packet rates and TX timestamp accuracy > with ntpperf. While the HW TX timestamping seems more reliable at some > lower request rates, there seems to be about 40% drop in the overall > performance of the server in how much requests it can handle (falling > back to SW timestamps when HW timestamp is missed). Is this expected > or something to be considered?
Thanks for testing! Nope, this is not really expected. Let me see if I can reproduce your results and see where that comes from. Thanks, Kurt
signature.asc
Description: PGP signature
