From: Andy Smith <andy@strugglers.net>
To: xen-devel@lists.xen.org
Subject: Re: Limited range for counters in /sys/class/net/<vifname>/statistics/{r, t}x_bytes - 33 bits?
Date: Sun, 3 Sep 2017 04:27:12 +0000 [thread overview]
Message-ID: <20170903042712.GB19832@bitfolk.com> (raw)
In-Reply-To: <20170903031046.GA19832@bitfolk.com>
Hello,
On Sun, Sep 03, 2017 at 03:10:46AM +0000, Andy Smith wrote:
> Is this intentional?
I see from:
http://elixir.free-electrons.com/linux/v4.9.47/source/drivers/net/xen-netback/interface.c#L228
and:
http://elixir.free-electrons.com/linux/v4.10/source/drivers/net/xen-netback/interface.c#L224
that the counters went from an unsigned long to a u64 so I think
that answers my question and it was a bug/deficiency that was fixed.
Oh well, should anyone else not yet using a 4.10+ kernel experience
this, maybe they will do a search and find these posts and not pull
their hair out. :)
Cheers,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-03 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 3:10 Limited range for counters in /sys/class/net/<vifname>/statistics/{r, t}x_bytes - 33 bits? Andy Smith
2017-09-03 4:27 ` Andy Smith [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=20170903042712.GB19832@bitfolk.com \
--to=andy@strugglers.net \
--cc=xen-devel@lists.xen.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.