From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Danny Gonzalez <digonzal@google.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
David Decotigny <decot@google.com>,
"Anjali Singhai" <anjali.singhai@intel.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Brian Vazquez <brianvv@google.com>, Li Li <boolli@google.com>,
<emil.s.tantilov@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH iwl-net] idpf: decrease statistics refresh interval
Date: Fri, 12 Jun 2026 11:29:45 +0200 [thread overview]
Message-ID: <7a6a3f63-0b69-4e1f-997e-f198e2bc43e9@intel.com> (raw)
In-Reply-To: <CAH1CuA-zQveU_pzopVMnDM11Kbz8wTzMP=SvSDBEq8Tk3RaebQ@mail.gmail.com>
From: Danny Gonzalez <digonzal@google.com>
Date: Thu, 11 Jun 2026 11:26:18 -0700
> On Thu, Jun 11, 2026 at 8:57 AM Alexander Lobakin
> <aleksander.lobakin@intel.com> wrote:
>>
>> From: Danny Gonzalez <digonzal@google.com>
>> Date: Thu, 11 Jun 2026 00:24:37 +0000
>>
>>> The default 10s statistics refresh interval is too slow for real-time
>>> monitoring and causes network selftests (e.g., uso.py) to fail when
>>> verifying traffic immediately after transmission.
>>>
>>> A 10s delay also causes aliasing in telemetry tools polling at shorter
>>> intervals (e.g., 5s), leading to inaccurate rate calculations on
>>> high-throughput NICs.
>>>
>>> Decrease the refresh interval to 250ms to ensure fresh stats and fix
>>> test failures.
>>
>> Have you tried a bit more conservate value like 1s? Wouldn't it be
>> enough for tests to pass?
>>
>> 250 ms is also okay, just curious.
>
> Yes, 1s also allows the tests to pass.
>
> We have a preference for 250 ms since High-Freq Telemetry (1s poll)
> 1s driver refresh rate causes aliasing:
>
> # sar -n DEV 1 | grep eth1
> 10:52:15 eth1 390.00 339.00 51.92 55.54
> 0.00 0.00 0.00 0.00
> 10:52:16 eth1 409.00 360.00 54.72 58.64
> 0.00 0.00 0.00 0.00
> 10:52:17 eth1 0.00 0.00 0.00 0.00
> 0.00 0.00 0.00 0.00
Ack!
Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>
>
> Thanks,
> Danny
Thanks,
Olek
next prev parent reply other threads:[~2026-06-12 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 0:24 Danny Gonzalez
2026-06-11 15:10 ` Brian Vazquez
2026-06-11 15:57 ` Alexander Lobakin
2026-06-11 18:26 ` Danny Gonzalez
2026-06-12 9:29 ` Alexander Lobakin [this message]
2026-06-12 18:28 ` Tantilov, Emil S
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=7a6a3f63-0b69-4e1f-997e-f198e2bc43e9@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=anjali.singhai@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=boolli@google.com \
--cc=brianvv@google.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=digonzal@google.com \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=sridhar.samudrala@intel.com \
--cc=stable@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
all inboxes | Powered by JetHome®