From: Phil Dibowitz <phil@ipom.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: reminder, 2.6.18 window...
Date: Wed, 24 May 2006 11:56:45 -0700 [thread overview]
Message-ID: <20060524185644.GF22881@ipom.com> (raw)
In-Reply-To: <4474A489.4080308@garzik.org>
[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]
On Wed, May 24, 2006 at 02:23:05PM -0400, Jeff Garzik wrote:
> I disagree that we should bother about clearing statistics. It always
> adds more complication than necessary. Few (if any) other statistics in
> Linux permit easy clearing, often because adding operations other than
> 'increment' or 'read' requires adding expensive spinlocks or atomic
> operations.
Every networking device in the world supports clearing interface statistics.
Why should linux not be able to do the most basic operation on any
cisco/juniper/enterasys/whatever managed switch or router?
It's a common operation on a network interface, I don't see why this is a
concern.
When I'm debugging a networking issue On a cluster of hundreds and hundreds
of machines at work, I want to be able to reset them all quickly, and get a
rough idea of if they're all climbing, if they're all climbing at the same
rate, etc. And being able to do "for i in `cat hostlist`; do ssh $i ethtool -z
eth0; done" is really, really, REALLY, useful.
As for SNMP statistics, again, this is just like clearing stats on any other
platform - it's a manual thing... you're *choosing* to reset the stats, and
accept the consequences. Its not like the patch introduces some nightly
resetting - it's just an _option_ to users
It's about providing an option that requires no extra complications in the
code (at least in this case), and that has been requested on every
sysadmin-related list I'm on, and in most cases is a re-occuring topic.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-24 18:56 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 [this message]
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
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=20060524185644.GF22881@ipom.com \
--to=phil@ipom.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.