From: Thomas Davis <tadavis@lbl.gov>
To: Jeff Golds <jgolds@resilience.com>
Cc: Laurent Itti <itti@java.usc.edu>, linux-kernel@vger.kernel.org
Subject: Re: receive stats null for bond0 in 2.4.6
Date: Thu, 12 Jul 2001 13:21:57 -0700 [thread overview]
Message-ID: <3B4E06E5.899CAD8E@lbl.gov> (raw)
In-Reply-To: <Pine.SV4.3.96.1010711163709.5481B-100000@java.usc.edu> <3B4CF00C.5B62DDBA@resilience.com> <3B4DF1A8.BDE85995@lbl.gov> <3B4E02BD.7A9087E2@resilience.com>
Jeff Golds wrote:
>
> So what's wrong with collecting the slaves' receive stats and reporting
> them as stats for the bonding driver? At least then you can quickly see
> the total for all devices currently owned by the bonding device.
>
> Stats are just a tool so that you can see if things are behaving
> properly, you can report back whatever you like. I prefer to have the
> bonding driver collect the slaves' stats so you can easily see if
> enslaved devices are receiving packets. If you want to see which device
> is getting more traffic, that's easy to see by looking at the individual
> slave.
>
the person who ported the driver over to 2.4 from 2.2 made that choice.
It wasn't me. It was one of the network guys (Dave/Alexy/??).
One problem with collecting all the stats into the bonding driver -
which I have seen, is you can quickly start to overflow counters. And
they don't roll over.
--
------------------------+--------------------------------------------------
Thomas Davis | ASG Cluster guy
tadavis@lbl.gov |
(510) 486-4524 | "80 nodes and chugging Captain!"
prev parent reply other threads:[~2001-07-12 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 23:47 receive stats null for bond0 in 2.4.6 Laurent Itti
2001-07-12 0:32 ` Jeff Golds
2001-07-12 0:32 ` Laurent Itti
2001-07-12 18:51 ` Thomas Davis
2001-07-12 20:04 ` Jeff Golds
2001-07-12 20:21 ` 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=3B4E06E5.899CAD8E@lbl.gov \
--to=tadavis@lbl.gov \
--cc=itti@java.usc.edu \
--cc=jgolds@resilience.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