From: Thomas Davis <tadavis@lbl.gov>
To: Chris Chabot <chabotc@reviewboard.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interface statistics for Bonding bug in 2.4
Date: Mon, 22 Jan 2001 10:15:05 -0800 [thread overview]
Message-ID: <3A6C78A9.1EB43322@lbl.gov> (raw)
In-Reply-To: <3A6CF2EB.7EB23951@reviewboard.com>
The answer is in the source; in v2.4, stats are only collected on sent
packets; in v2.2, stats are not collected at all; they are simply summed
from the interfaces stats.
It's not a bug; it's simply a design decision.
Chris Chabot wrote:
>
> I recently upgraded my main server to a 2.4 kernel (2.4.1pre9). This
> machine uses 2 3Com 3C905B networkcards, bonded together (using the
> bonding module).
>
> When doing a 'ifconfig' the bond0 device shows 0 RX packets, and a valid
> # of TX packets. However looking at eth0 / eth1 (the 2 network cards)
> they have the just about the same amount of RX packets, so recieving
> does apear to be balanced over the two interfaces.
>
> When running this machine on 2.2.16 the interface it does show the
> interface statistics accuratly. I also tested this on a clean 2.4.0
> kernel, and it had the same bug.
>
> The ifconfig output (note the 0 packets in bond0's RX)
>
> bond0 Link encap:Ethernet HWaddr 00:50:DA:B8:33:0F
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
>
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3655 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> eth0 Link encap:Ethernet HWaddr 00:50:DA:B8:33:0F
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
>
> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> RX packets:1992 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1828 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:11 Base address:0x9800
>
> eth1 Link encap:Ethernet HWaddr 00:50:DA:B8:33:0F
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
>
> UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
> RX packets:1878 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1827 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:10 Base address:0x9400
>
> Please CC me in any replies since im not subscribed to the kernel list.
>
> -- Chris
--
------------------------+--------------------------------------------------
Thomas Davis | PDSF Project Leader
tadavis@lbl.gov |
(510) 486-4524 | "Only a petabyte of data this year?"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-22 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 2:56 Interface statistics for Bonding bug in 2.4 Chris Chabot
2001-01-22 18:15 ` Thomas Davis [this message]
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=3A6C78A9.1EB43322@lbl.gov \
--to=tadavis@lbl.gov \
--cc=chabotc@reviewboard.com \
--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