netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Liblit <liblit@acm.org>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, 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:16 -0500	[thread overview]
Message-ID: <481F9E64.6070606@acm.org> (raw)
In-Reply-To: <20080505.161806.267621711.davem@davemloft.net>

Perhaps userspace needs a way to tweak the update frequency?  Or perhaps 
the driver needs a way to tell userspace what update frequency it should 
expect?  Without some kind of coordination, we have the present silly 
situation: userspace network activity monitors are checking rx_bytes 
more frequently than could possibly be useful.

Do different Ethernet drivers update rx_bytes at the same rate?  Or is 
this completely ad hoc?

  reply	other threads:[~2008-05-05 23:56 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 [this message]
2008-05-06  1:17       ` Michael Chan
2008-05-06  0:43         ` Krzysztof Oledzki
2008-05-06  1:55           ` Michael Chan
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=481F9E64.6070606@acm.org \
    --to=liblit@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=davem@davemloft.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).