Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: remove rx_len_errors statistic
Date: Mon, 20 Nov 2023 13:48:26 -0800	[thread overview]
Message-ID: <705464ad-8559-4096-a31f-4f4b6fc05770@intel.com> (raw)
In-Reply-To: <20231120112726.149409-1-jan.sokolowski@intel.com>



On 11/20/2023 3:27 AM, Jan Sokolowski wrote:
> It was found that this statistic is incorrectly reported
> by HW and thus, useless.
> 
> Remove it.

Is there any further information about what is reported incorrectly? Is
rx_length_errors part of netdev stats and standardized? Does HW fail to
report some packets or does it report packets which don't have an issue?

I mean the hardware does *something*, so I think it would be good to
have an understanding of how this differs from what we expected when
proposing to remove it.

Thanks,
Jake
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-11-20 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 11:27 [Intel-wired-lan] [PATCH iwl-next v1] ice: remove rx_len_errors statistic Jan Sokolowski
2023-11-20 21:48 ` Jacob Keller [this message]
2023-11-29 10:26   ` Sokolowski, Jan
2023-11-29 11:03     ` Przemek Kitszel
  -- strict thread matches above, loose matches on Subject: below --
2023-12-06 10:43 Jan Sokolowski
2023-12-07 23:33 ` Tony Nguyen
2023-12-11  4:58 ` Pucha, HimasekharX Reddy

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=705464ad-8559-4096-a31f-4f4b6fc05770@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.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