From: jamal <hadi@cyberus.ca>
To: Phil Dibowitz <phil@ipom.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: reminder, 2.6.18 window...
Date: Wed, 24 May 2006 16:10:32 -0400 [thread overview]
Message-ID: <1148501433.5325.52.camel@jzny2> (raw)
In-Reply-To: <20060524191442.GG22881@ipom.com>
On Wed, 2006-24-05 at 12:14 -0700, Phil Dibowitz wrote:
>
> Right, I'm aware there are other ways of doing this - I've written scripts to
> record a hundreds of numbers, and then subtract them from each other. But
> those scripts are work arounds
It is not a work around, _it is design intent_. It is what network
management tools have been expecting since the days of the caveman.
These stats are supposed to be monotonically increasing; if that
behavior is contradicted, a rollover of the counters is assumed.
> for a feature _lacking_ in the kernel. A
> feature that, as I've mentioned, is supported on any piece of networking gear
> (and of course, lets not forget there's a specific option in the kernel config
> *just* for "behave like a router").
Can you provide some link to a vendor that allows resetting ethernet
stats? I am almost certain, if they do they will have something or other
which indicates that such a reset happened. It is also easier for cisco
to have none standard feature "as of ios 15.16" which could support such
behavior because they bundle everything including network management
tools. We dont have that luxury. The BSDs may actually get away with it
because they bundle user space apps as well. Perhaps some
random Linux vendor as well..
> If my patch was invasive and broke things,
It _does break_ things for all known management apps.
This is not to say it is not useful for testing, development or
debugging (which is what you seem to be using it for) but it does mean
it is broken.
cheers,
jamal
next prev parent reply other threads:[~2006-05-24 20:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 1:22 reminder, 2.6.18 window David Miller
2006-05-24 8:01 ` Phil Dibowitz
2006-05-24 18:21 ` jamal
2006-05-24 18:23 ` Jeff Garzik
2006-05-24 18:34 ` Rick Jones
2006-05-24 18:56 ` Phil Dibowitz
2006-05-24 19:05 ` Jeff Garzik
2006-05-24 19:14 ` Phil Dibowitz
2006-05-24 20:01 ` Brent Cook
2006-05-24 20:08 ` Jeff Garzik
2006-05-25 7:23 ` Bill Fink
2006-05-25 13:05 ` Brent Cook
2006-05-25 16:12 ` Bill Fink
2006-05-25 17:59 ` Phil Dibowitz
2006-05-25 18:41 ` Brent Cook
2006-05-25 19:22 ` Phil Dibowitz
2006-05-25 20:29 ` David Miller
2006-05-25 21:04 ` Phil Dibowitz
2006-05-25 21:07 ` David Miller
2006-05-26 9:52 ` Andi Kleen
2006-05-25 13:34 ` Dave Dillow
2006-05-26 9:46 ` Andi Kleen
2006-05-24 20:10 ` jamal [this message]
2006-05-24 20:25 ` Rick Jones
2006-05-25 15:27 ` jamal
2006-05-25 16:43 ` Rick Jones
2006-05-26 22:06 ` Rick Jones
2006-05-24 20:44 ` Brian Haley
2006-05-24 21:01 ` Rick Jones
2006-05-26 6:48 ` Phil Dibowitz
2006-05-24 20:48 ` Phil Dibowitz
2006-05-24 21:04 ` Rick Jones
2006-05-24 21:10 ` Ben Greear
2006-05-25 5:01 ` Phil Dibowitz
2006-05-25 7:18 ` Ben Greear
2006-05-25 7:55 ` Bill Fink
2006-05-25 12:17 ` Francois Romieu
2006-05-25 9:53 ` Pekka Savola
2006-05-24 20:53 ` Andy
2006-05-26 9:43 ` Andi Kleen
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=1148501433.5325.52.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=phil@ipom.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).