DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: LukeSeewald <luke.seewald@gmail.com>
Cc: <anatoly.burakov@intel.com>, <dev@dpdk.org>, <luke@aterlo.com>
Subject: Re: [PATCH] net/ice: enlarge limits to 64 bits (ice_stats_get)
Date: Mon, 12 May 2025 17:04:20 +0100	[thread overview]
Message-ID: <aCIcBLJyohs6H3gh@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250403135041.1377720-1-luke.seewald@gmail.com>

On Thu, Apr 03, 2025 at 09:50:41AM -0400, LukeSeewald wrote:
> There are various counters/stats coming from ice_stats_get that appear
> to only use 32 or 40 bits and once it hits that limit it "overflows"
> and resets. This was causing large spikes (sudden 2^42 increase from
> one second to the next) in values of ibytes and obytes, while causing
> sudden drops in opackets and ipackets (as they "overflow" and reset).
> The sudden spike in bytes is due to the packets count being multiplied
> by 4 (crc bytes) and subtracted from the byte count. E.g. One second
> the packet count could be just under the 40 bit limit, subtracting a
> very large number from the byte count and then in the next second hit
> the limit, "overflow" and reset subtracting a very small number, thus
> causing the byte counts to appear as if there was a large increase in a
> single second.
> 
> This patch fixes the issue by enlarging the limitations of any counters
> or stats used by ice_stats_get to 64 bits, following the pattern of a
> previous patch -
> https://mails.dpdk.org/archives/stable/2020-July/023940.html
> 
> Signed-off-by: LukeSeewald <luke.seewald@gmail.com>
> ---
>  drivers/net/intel/ice/ice_ethdev.c | 103 +++++++++++++++++++++--------
>  drivers/net/intel/ice/ice_ethdev.h |  44 ++++++++++--
>  2 files changed, 115 insertions(+), 32 deletions(-)
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>


       reply	other threads:[~2025-05-12 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250403135041.1377720-1-luke.seewald@gmail.com>
2025-05-12 16:04 ` Bruce Richardson [this message]
2025-05-12 16:19   ` Bruce Richardson
2025-04-03 14:49 LukeSeewald

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=aCIcBLJyohs6H3gh@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=luke.seewald@gmail.com \
    --cc=luke@aterlo.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;
as well as URLs for NNTP newsgroup(s).