All of lore.kernel.org
 help / color / mirror / Atom feed
From: Atom2 <ariel.atom2@web2web.at>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: BUG - xen-netback stats interface limited to 32-bit values on 64 bit systems
Date: Thu, 12 Feb 2015 20:47:58 +0100	[thread overview]
Message-ID: <54DD036E.4060706@web2web.at> (raw)
In-Reply-To: <1423480148.23098.36.camel@citrix.com>

Hi guys,
I am forwarding this message after initially having confirmed with Ian 
Campbell on the user list that there's really an issue - please see 
further below.

I am currently running xen-4.3.3 on gentoo (dom0 is based on kernel 
3.17.7) and I am happy to help out by applying and testing patches on my 
version.

Thanks Atom2

-------- Weitergeleitete Nachricht --------
Betreff: Re: [Xen-users] BUG? vif RX/TX byte counters limited to 32-bit 
values on 64 bit systems
Datum: Mon, 9 Feb 2015 11:09:08 +0000
Von: Ian Campbell <ian.campbell@citrix.com>
An: Atom2 <ariel.atom2@web2web.at>
Kopie (CC): xen-users@lists.xen.org

On Mon, 2015-02-09 at 00:37 +0100, Atom2 wrote:
> Hi guys,
> I recently experienced that ifconfig executed within dom0 wraps around
> byte counters after reaching the 32-bit max value (2^32) for XEN vif
> interfaces. Specifically I was able to observe this for a XEN vif
> interface connected to a HVM domU running FreeBSD 10.0.

Looks like xen-netback was never converted to the 64 bit stats interface
like e.g. netfront was (see commit e00f85bec0a9 in ~v3.1).

I could have sworn netback changed eons ago -- I was clearly mistaken.

Ian.

       reply	other threads:[~2015-02-12 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1423480148.23098.36.camel@citrix.com>
2015-02-12 19:47 ` Atom2 [this message]
2015-02-18 15:24   ` BUG - xen-netback stats interface limited to 32-bit values on 64 bit systems Ian Campbell
2015-02-18 15:30     ` Processed: " xen
2015-02-18 17:57     ` Atom2
2015-02-19  9:51       ` Ian Campbell

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=54DD036E.4060706@web2web.at \
    --to=ariel.atom2@web2web.at \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xenproject.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.