From: Jeff Garzik <jeff@garzik.org>
To: Brent Cook <bcook@bpointsys.com>
Cc: Phil Dibowitz <phil@ipom.com>, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: reminder, 2.6.18 window...
Date: Wed, 24 May 2006 16:08:50 -0400 [thread overview]
Message-ID: <4474BD52.6020604@garzik.org> (raw)
In-Reply-To: <200605241501.53477.bcook@bpointsys.com>
Brent Cook wrote:
> Note that this is just clearing the hardware statistics on the interface, and
> would not require any kind of atomic_increment addition for interfaces that
> support that. It would be kind-of awkward to implement this on drivers that
> increment stats in hardware though (lo, vlan, br, etc.) This also brings up
> the question of resetting the stats for 'netstat -s'
If you don't atomically clear the statistics, then you are leaving open
a window where the stats could easily be corrupted, if the network
interface is under load.
This 'clearing' operation has implications on the rest of the statistics
usage.
More complexity, and breaking of apps, when we could just use the
existing, working system? I'll take the "do nothing, break nothing,
everything still works" route any day.
> What would be great is if ifconfig, netstat and their ilk just had a -z flag
> instead. This would write a file to the local user's home directory with a
> stats snapshot, and then every subsequent run would auto-calculate against
> the snapshot. You'd also need some way of resetting this when the stats
> actually _do_ reset (driver reload, reboot.) to avoid negative numbers.
> That way, you can get what you want without having to write a bunch of
> fragile, awkward scripts, and the kernel isn't throwing away information
> either.
See... this opens doors to tons of complexity.
Jeff
next prev parent reply other threads:[~2006-05-24 20:08 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 [this message]
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=4474BD52.6020604@garzik.org \
--to=jeff@garzik.org \
--cc=bcook@bpointsys.com \
--cc=davem@davemloft.net \
--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).