From: Grant Coady <gcoady@gmail.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: 2.4: e100 accounting bust for multiple adapters
Date: Wed, 11 Jan 2006 12:35:35 +1100 [thread overview]
Message-ID: <cln8s1diqmsei30gqo0dbuv1hclgl4m2lu@4ax.com> (raw)
In-Reply-To: <4807377b0601101624m1e1eb636q99ae0792b0903c5a@mail.gmail.com>
On Tue, 10 Jan 2006 16:24:28 -0800, Jesse Brandeburg <jesse.brandeburg@gmail.com> wrote:
>On 1/9/06, Grant Coady <gcoady@gmail.com> wrote:
>> Hi there,
>>
>> While testing for a different issue on a box with two e100 NICs I noticed
>> that interrupt and other accounting are accumulated to the first e100 NIC.
>
>are the two e100's on the same broadcast domain? if they are you
>might actually be transferring all traffic on eth0
You ignore the fact these two NICs work as expected on 2.6.15
and on 2.4.32 when e100 driver is compiled in, for the same
hardware and test.
>
>e100 doesn't track its own interrupt counts, the kernel does that for us.
What further testing would you like? Also, you ignore the all
zeroes ifconfig accounting for the second NIC, and that the
accounting was also accumulated to the first e100 along with
interrupts.
Anyway the solution is simple: modular e100 is borked on 2.4,
compiled in is okay.
Grant.
next prev parent reply other threads:[~2006-01-11 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 3:07 2.4: e100 accounting bust for multiple adapters Grant Coady
2006-01-11 0:24 ` Jesse Brandeburg
2006-01-11 1:35 ` Grant Coady [this message]
2006-01-12 4:59 ` Jesse Brandeburg
2006-01-14 2:55 ` Grant Coady
2006-01-14 7:50 ` Jesse Brandeburg
2006-01-14 8:24 ` Grant Coady
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=cln8s1diqmsei30gqo0dbuv1hclgl4m2lu@4ax.com \
--to=gcoady@gmail.com \
--cc=jesse.brandeburg@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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).