From: Michael Chan <michael.chan@broadcom.com>
To: David Laight <David.Laight@aculab.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mchan@broadcom.com" <mchan@broadcom.com>,
David Miller <davem@davemloft.net>,
Pavan Chebbi <pavan.chebbi@broadcom.com>
Subject: Re: tg3 dropping packets at high packet rates
Date: Wed, 18 May 2022 17:52:13 -0700 [thread overview]
Message-ID: <CACKFLinwh=YgPGPZ0M0dTJK1ar+SoPUZtYb5nBmLj6CNPdCQ2g@mail.gmail.com> (raw)
In-Reply-To: <153739175cf241a5895e6a5685a89598@AcuMS.aculab.com>
On Wed, May 18, 2022 at 2:31 PM David Laight <David.Laight@aculab.com> wrote:
>
> From: Paolo Abeni
> > Sent: 18 May 2022 18:27
> ....
> > > If I read /sys/class/net/em2/statistics/rx_packets every second
> > > delaying with:
> > > syscall(SYS_clock_nanosleep, CLOCK_MONOTONIC, TIMER_ABSTIME, &ts, NULL);
> > > about every 43 seconds I get a zero increment.
> > > This really doesn't help!
> >
> > It looks like the tg3 driver fetches the H/W stats once per second. I
> > guess that if you fetch them with the same period and you are unlucky
> > you can read the same sample 2 consecutive time.
>
> Actually I think the hardware is writing them to kernel memory
> every second.
On your BCM95720 chip, statistics are gathered by tg3_timer() once a
second. Older chips will use DMA.
Please show a snapshot of all the counters. In particular,
rxbds_empty, rx_discards, etc will show whether the driver is keeping
up with incoming RX packets or not.
next prev parent reply other threads:[~2022-05-19 0:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:08 tg3 dropping packets at high packet rates David Laight
2022-05-18 17:27 ` Paolo Abeni
2022-05-18 21:31 ` David Laight
2022-05-19 0:52 ` Michael Chan [this message]
2022-05-19 8:44 ` David Laight
2022-05-19 10:20 ` Pavan Chebbi
2022-05-19 13:14 ` David Laight
2022-05-19 13:29 ` Paolo Abeni
2022-05-19 13:54 ` Andrew Lunn
2022-05-19 14:11 ` David Laight
2022-05-19 14:35 ` Pavan Chebbi
2022-05-19 14:42 ` David Laight
2022-05-20 16:08 ` David Laight
2022-05-23 16:01 ` David Laight
2022-05-23 16:14 ` Pavan Chebbi
2022-05-23 21:23 ` David Laight
2022-05-25 7:28 ` David Laight
2022-05-25 15:56 ` Jakub Kicinski
2022-05-25 21:48 ` David Laight
2022-05-22 23:22 ` Michael Chan
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='CACKFLinwh=YgPGPZ0M0dTJK1ar+SoPUZtYb5nBmLj6CNPdCQ2g@mail.gmail.com' \
--to=michael.chan@broadcom.com \
--cc=David.Laight@aculab.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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).