From: Ben Liblit <liblit@acm.org>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Michael Chan <mchan@broadcom.com>,
David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, netdev <netdev@vger.kernel.org>,
bugme-daemon@bugzilla.kernel.org, "Ronciak,
John" <john.ronciak@intel.com>
Subject: Re: [Bugme-new] [Bug 10600] New: e1000 updates rx_bytes infrequently
Date: Mon, 12 May 2008 01:42:34 -0500 [thread overview]
Message-ID: <4827E6DA.2050503@acm.org> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52051AB314@orsmsx418.amr.corp.intel.com>
Jesse Brandeburg wrote:
> I found that these commits (to do real time stats update) are in
> 2.6.25-rc1, not 2.6.24, it would be great if you were able to try a
> newer kernel version to verify that these fixes work for you.
I'm now running a self-built 2.6.25.3 kernel. I confirm that rx_bytes
updates as frequently as I'm reasonably able to check it.
Furthermore, the e1000e driver included with 2.5.25.3 works on my
hardware when using this kernel. Both e1000 and e1000e work, and
rx_bytes is updated promptly when using either driver.
Problem solved.
next prev parent reply other threads:[~2008-05-12 6:42 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
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 [this message]
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=4827E6DA.2050503@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=mchan@broadcom.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).