public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: Ethan Weinstein <lists@stinkfoot.org>, linux-kernel@vger.kernel.org
Subject: Re: minor e1000 bug
Date: Sat, 20 Dec 2003 13:46:27 +0100	[thread overview]
Message-ID: <200312201346.27044.hpj@urpla.net> (raw)
In-Reply-To: <3FE3623D.9000706@stinkfoot.org>

Hi Ethan,

On Friday 19 December 2003 21:40, Ethan Weinstein wrote:
> 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

Every 2 seconds exactly.

I would also be interested in a statement from intel fellows on the 
reasoning behind this decision, since every user of gkrellm will 
notice some strange behaviour (value oscillating between 0 and 
throughput * 2). (Poor man's real time bandwidth management ;-). 

After being tired of cognitive interpretation of these values, I 
decided to fix it, which was pretty easy:

--- linux-2.4.20/drivers/net/e1000/e1000_main.c~    2003-08-03 00:40:21.000000000 +0200
+++ linux-2.4.20/drivers/net/e1000/e1000_main.c 2003-08-08 13:20:06.000000000 +0200
@@ -1390,7 +1390,7 @@
        netif_stop_queue(netdev);
 
    /* Reset the timer */
-   mod_timer(&adapter->watchdog_timer, jiffies + 2 * HZ);
+   mod_timer(&adapter->watchdog_timer, jiffies + HZ);
 }
 
 #define E1000_TX_FLAGS_CSUM        0x00000001


> interval that might be modified within the driver to fix this?  It
> screws up realtime bandwidth measurements for these cards.
>
>
> -Ethan

Enjoy,
Pete


  reply	other threads:[~2003-12-20 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 20:40 minor e1000 bug Ethan Weinstein
2003-12-20 12:46 ` Hans-Peter Jansen [this message]
  -- 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=200312201346.27044.hpj@urpla.net \
    --to=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@stinkfoot.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