From: Ethan Weinstein <lists@stinkfoot.org>
To: linux-kernel@vger.kernel.org
Subject: minor e1000 bug
Date: Fri, 19 Dec 2003 15:40:29 -0500 [thread overview]
Message-ID: <3FE3623D.9000706@stinkfoot.org> (raw)
I've noticed that the e1000 driver does not update the counters in
/proc/net/dev as quickly as several other drivers I've tried, such as
e100 (both the Becker driver, and Intel's), sk90lin, and 3c59x. These
drivers seem to update the counters in a very timely fashion while the
e1000 driver doesn't seem to update them for several seconds. This is
apparent in 2.6.0, and 2.4.xx. Is there an update interval that might be
modified within the driver to fix this? It screws up realtime bandwidth
measurements for these cards.
-Ethan
next reply other threads:[~2003-12-20 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 20:40 Ethan Weinstein [this message]
2003-12-20 12:46 ` minor e1000 bug Hans-Peter Jansen
-- strict thread matches above, loose matches on Subject: below --
2003-12-22 5:26 Feldman, Scott
2003-12-22 10:26 ` Hans-Peter Jansen
2003-12-22 15:26 ` Ethan Weinstein
2003-12-22 19:30 Feldman, Scott
2003-12-22 19:52 ` Ethan Weinstein
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E0103424209@orsmsx402.jf.intel.com>
2003-12-24 0:29 ` Feldman, Scott
2003-12-23 14:54 ` Ethan Weinstein
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=3FE3623D.9000706@stinkfoot.org \
--to=lists@stinkfoot.org \
--cc=linux-kernel@vger.kernel.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