(Sorry for breaking the thread, please CC me on future replies...)
If I understand the discussion correctly, the problem in itself isn't greater
then that different methods of gathering the statistics have different
rollovers and thus confuse people who aren't aware of which method each tool
uses.
From: "Chris Friesen" <[EMAIL PROTECTED]>
Date: Tue, 10 Jul 2007 12:17:12 -0600
> It's rather ironic that the "new-and-improved" way of doing things is
> subject to rollover while the "old" way is not.
Text is always more flexible, but is hard to extend.
We can trivially add "u64" statistics to
David Miller wrote:
It used unsigned long ages ago, and ifconfig gets the bits
exported from /proc/net/dev output whereas we have to used
fixed data types in whatever we use over netlink so u32
was choosen.
It's rather ironic that the "new-and-improved" way of doing things is
subject to rollo
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Tue, 10 Jul 2007 08:56:40 -0700
> Looks like net_device_stats should have always used u32?
It used unsigned long ages ago, and ifconfig gets the bits
exported from /proc/net/dev output whereas we have to used
fixed data types in whatever we use ov
Looks like net_device_stats should have always used u32?
Too late to change it now.
Begin forwarded message:
Date: Tue, 10 Jul 2007 13:58:51 +0200
From: Andreas Henriksson <[EMAIL PROTECTED]>
To: netdev@vger.kernel.org
Cc: [EMAIL PROTECTED]
Subject: iproute2 showing wrong number of by
Hello!
While investigating the problems reported in Debian bug #199054
(http://bugs.debian.org/199054), stating that the RX/TX bytes differ between
ifconfig and ip(route2) I came across this:
include/linux/if_link.h (used in kernel and iproute2 source):
/* The struct should be in sync with struct
