From: Stephen Hemminger <shemminger@linux-foundation.org>
To: netdev@vger.kernel.org
Subject: Re: 64bit counters: iproute(netlink) vs ifconfig
Date: Wed, 13 Feb 2008 12:35:09 -0800 [thread overview]
Message-ID: <20080213123509.7bff7b7b@extreme> (raw)
In-Reply-To: <Pine.LNX.4.64.0802132114110.16999@bizon.gios.gov.pl>
On Wed, 13 Feb 2008 21:20:59 +0100 (CET)
Krzysztof Oledzki <olel@ans.pl> wrote:
> Hello,
>
> Just discovered that counters returned by the "ip" tool are truncated:
>
> # ip -s link show bond0
> 1: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue
> link/ether 00:1d:09:67:6e:2f brd ff:ff:ff:ff:ff:ff
> RX: bytes packets errors dropped overrun mcast
> 2485605521 9010211 0 0 0 6
> TX: bytes packets errors dropped carrier collsns
> 3023237974 9345397 0 0 0 0
>
> # ifconfig bond0
> bond0 Link encap:Ethernet HWaddr 00:1D:09:67:6E:2F
> inet addr:192.168.152.62 Bcast:192.168.152.255 Mask:255.255.255.0
> inet6 addr: fe80::21d:9ff:fe67:6e2f/64 Scope:Link
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:9010367 errors:0 dropped:351 overruns:0 frame:0
> TX packets:9345521 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2485631020 (2370.4 Mb) TX bytes:7318232294 (6979.2 Mb)
>
> Is it possible to get 64-bit counters in ip via netlink? Struct
> rtnl_link_stats does not look very optimistic, as it has rx_bytes/tx_bytes
> defined with __u32.
>
> Best regards,
>
> Krzysztof Olędzki
The problem is the kernel binary API is now hard coded to 32 bit values.
--
Stephen Hemminger <stephen.hemminger@vyatta.com>
prev parent reply other threads:[~2008-02-13 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 20:20 64bit counters: iproute(netlink) vs ifconfig Krzysztof Oledzki
2008-02-13 20:35 ` Stephen Hemminger [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=20080213123509.7bff7b7b@extreme \
--to=shemminger@linux-foundation.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 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).