From: "Michael Chan" <mchan@broadcom•com>
To: "Krzysztof Oledzki" <olel@ans•pl>
Cc: "Ben Liblit" <liblit@acm•org>,
"David Miller" <davem@davemloft•net>,
akpm@linux-foundation•org, netdev <netdev@vger•kernel.org>,
bugme-daemon@bugzilla•kernel.org, jesse.brandeburg@intel•com,
john.ronciak@intel•com
Subject: Re: [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently
Date: Mon, 05 May 2008 18:55:49 -0700 [thread overview]
Message-ID: <1210038949.7941.189.camel@dell> (raw)
In-Reply-To: <Pine.LNX.4.64.0805060235410.6134@bizon.gios.gov.pl>
On Tue, 2008-05-06 at 02:43 +0200, Krzysztof Oledzki wrote:
> Hm... strange - I tested it on 2.6.23.17 with:
> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 12)
>
> Setting both:
> # ethtool -C eth0 stats-block-usecs 50
> and:
> # ethtool -C eth0 stats-block-usecs 5000000
> gives exactly the same situation - statistics update frequency is
> still ~1s.
>
> # ethtool -c eth1 |grep stats-block-usecs
> stats-block-usecs: 999936
Unfortunately, 5708 has a bug in the statistics DMA engine that was
reported here on netdev about 1 year ago. To work around it, we have to
disable the statistics block DMA and rely on the driver's timer function
which runs at a fixed 1 second interval. So only 0 and 999936 are
allowed values on the 5708. Newer chips or the older 5706 do not have
this problem.
next prev parent reply other threads:[~2008-05-06 0:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10600-10286@http.bugzilla.kernel.org/>
2008-05-05 22:55 ` [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently Andrew Morton
2008-05-05 23:18 ` David Miller
2008-05-05 23:55 ` Ben Liblit
2008-05-06 1:17 ` Michael Chan
2008-05-06 0:43 ` Krzysztof Oledzki
2008-05-06 1:55 ` Michael Chan [this message]
2008-05-06 1:24 ` Ben Liblit
2008-05-06 17:22 ` Brandeburg, Jesse
2008-05-06 20:49 ` Brandeburg, Jesse
2008-05-12 5:44 ` Ben Liblit
2008-05-12 6:18 ` David Miller
2008-05-12 6:26 ` Ben Liblit
2008-05-12 6:42 ` Ben Liblit
2008-05-06 0:55 ` Michael Chan
2008-05-05 23:53 ` David Miller
2008-05-05 23:38 ` Ben Liblit
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=1210038949.7941.189.camel@dell \
--to=mchan@broadcom$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=john.ronciak@intel$(echo .)com \
--cc=liblit@acm$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olel@ans$(echo .)pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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