From: Jamie Lokier <jamie@shareable.org>
To: Avi Kivity <avi@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, Adam Litke <agl@us.ibm.com>
Subject: Re: [Qemu-devel] [RFC] virtio: Report new guest memory statistics pertinent to memory ballooning
Date: Sun, 8 Nov 2009 23:27:44 +0000 [thread overview]
Message-ID: <20091108232744.GA5275@shareable.org> (raw)
In-Reply-To: <4AF6891D.3080308@redhat.com>
Avi Kivity wrote:
> > (qemu) info balloon
> > balloon: actual=1024 MB
> > balloon: pswapin=0 pages
> > balloon: pswapout=0 pages
> > balloon: panon=3928 KB
> > balloon: pgmajfault=0
> > balloon: pgminfault=247914
> > balloon: memfree=987032 KB
> > balloon: memtot=1020812 KB
>
> It's important that these statistics be cross platform. Can you (or
> someone knowledgeable in Windows) verify that all of these are
> meaningful there? I'd expect it to be so with the possible exception of
> panon.
pswapin, pswapout, pgmajfault and pgminfault are not meaningful even
on some Linux targets (those without MMU, and therefore no page
faults). Yet even those could, perhaps, use virtio-balloon.
It's probably best to have a way to omit values that are not
meaningful to a guest, or otherwise indicate "not defined by the
current guest".
-- Jamie
next prev parent reply other threads:[~2009-11-08 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 22:50 [Qemu-devel] [RFC] virtio: Report new guest memory statistics pertinent to memory ballooning Adam Litke
2009-11-05 23:02 ` [Qemu-devel] virtio: Add memory statistics reporting to the balloon driver Adam Litke
2009-11-05 23:39 ` Anthony Liguori
2009-11-05 23:39 ` [Qemu-devel] " Anthony Liguori
2009-11-05 23:36 ` [Qemu-devel] Re: [RFC] virtio: Report new guest memory statistics pertinent to memory ballooning Anthony Liguori
2009-11-08 9:02 ` [Qemu-devel] " Avi Kivity
2009-11-08 23:27 ` Jamie Lokier [this message]
2009-11-09 13:59 ` Anthony Liguori
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=20091108232744.GA5275@shareable.org \
--to=jamie@shareable.org \
--cc=agl@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.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.