From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Pawel Chmielewski <pawel.chmielewski@intel.com>,
leszek.pepiak@intel.com, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] Lots of rx_long_byte_count errors
Date: Fri, 17 Nov 2023 13:13:10 +0100 [thread overview]
Message-ID: <dfbd2a81-6c2d-fb5f-c445-c3f65a0d0a76@intel.com> (raw)
In-Reply-To: <20231116104334.3ca31655@hermes.local>
On 11/16/23 19:43, Stephen Hemminger wrote:
> I am using builtin NIC on my little Brix box and surprised to see lots
> of byte count errors. Network seems a little sluggish at times.
> Do use locally NFS mounted NAS for storing things like kernel trees.
>
> $ lspci | grep Ethernet
> 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (13) I219-V (rev 20)
> ae:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 01)
>
> $ sudo ethtool -i enp174s0
> driver: igc
> version: 6.5.0-4-amd64
> firmware-version: 1045:740
> expansion-rom-version:
> bus-info: 0000:ae:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
> $ sudo ethtool -S enp174s0 | grep -v ': 0$'
> NIC statistics:
> rx_packets: 729954
> tx_packets: 222554
> rx_bytes: 867670928
here
> tx_bytes: 69174803
> rx_broadcast: 5002
> tx_broadcast: 37
> rx_multicast: 11959
> tx_multicast: 934
> multicast: 11959
> tx_tcp_seg_good: 1687
> tx_flow_control_xon: 32
> tx_flow_control_xoff: 31
> rx_long_byte_count: 867670928
this value is the same as rx_bytes above
Looking at the code it also looks like it's just a long (perhaps opposed
to just int counter) rx bytes count. No mention on errors.
No idea how much value it brings, but that's it not an error.
> tx_queue_0_packets: 22543
> tx_queue_0_bytes: 2712687
> tx_queue_1_packets: 4547
> tx_queue_1_bytes: 1486617
> tx_queue_2_packets: 103559
> tx_queue_2_bytes: 36988065
> tx_queue_3_packets: 14732
> tx_queue_3_bytes: 13193520
> rx_queue_0_packets: 112677
> rx_queue_0_bytes: 152437202
> rx_queue_1_packets: 91981
> rx_queue_1_bytes: 130521460
> rx_queue_2_packets: 231685
> rx_queue_2_bytes: 250398158
> rx_queue_3_packets: 11095
> rx_queue_3_bytes: 10376491
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-11-17 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 18:43 [Intel-wired-lan] Lots of rx_long_byte_count errors Stephen Hemminger
2023-11-17 12:13 ` Przemek Kitszel [this message]
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=dfbd2a81-6c2d-fb5f-c445-c3f65a0d0a76@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leszek.pepiak@intel.com \
--cc=pawel.chmielewski@intel.com \
--cc=stephen@networkplumber.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