qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	"agl@us.ibm.com" <agl@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"mdroth@linux.vnet.ibm.com" <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC 3/3] docs: document virtio-balloon stats
Date: Fri, 7 Dec 2012 16:54:44 -0200	[thread overview]
Message-ID: <20121207165444.163bbb4f@doriath.home> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75578606DB@lisa.maurer-it.com>

On Fri, 7 Dec 2012 15:01:36 +0000
Dietmar Maurer <dietmar@proxmox.com> wrote:

> > > Is it possible to extent those statistic to include buffer/cache values?
> > 
> > Yes, should be possible but the kernel virtio-balloon driver has to be
> > extended too (and I suspect this kind of change goes into the kernel first).
> 
> The current statistics are quite useless without that information, and

Maybe it's not possible to implement the feature you want to implement, but
I do get a ping once a while from people asking for these stats. Some of them
are people running virsh dommemstat which also makes use of that information.

> I guess it is impossible to such changes upstream within a reasonable time?

In the kernel, yes it would take a while.

> So what is the purpose of that 'stat-free-memory'? Can we change that to
> return the amount of free RAM including buffers?

That's kernel work, qemu is merely reporting what the kernel is making
available. But giving that you'll touch the kernel anyway, it's better
to add a new stat.

There are two other alternatives:

 1. add a query-memory-stats command to qemu-ga

     Pros: should be quicker and easier to modify/extend
     Cons: has the implications of running this from the guest user-space

 2. wait for the (kernel-based) auto-ballooning feature, which is on the
    works

     Pros: you do nothing and it's going to be completely automatic
     Cons: this is unlikely to be ready for the short term

  reply	other threads:[~2012-12-07 18:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 15:04 [Qemu-devel] [RFC 0/3] re-enable balloon stats Luiz Capitulino
2012-12-04 15:04 ` [Qemu-devel] [RFC 1/3] virtio-balloon: drop old stats code Luiz Capitulino
2012-12-04 15:04 ` [Qemu-devel] [RFC 2/3] virtio-balloon: re-enable balloon stats Luiz Capitulino
2012-12-06 17:03   ` mdroth
2012-12-06 17:58     ` Luiz Capitulino
2012-12-04 15:04 ` [Qemu-devel] [RFC 3/3] docs: document virtio-balloon stats Luiz Capitulino
2012-12-06 13:24   ` Daniel P. Berrange
2012-12-06 15:31     ` Luiz Capitulino
2012-12-06 16:59       ` mdroth
2012-12-07  5:30   ` Dietmar Maurer
2012-12-07 12:23     ` Luiz Capitulino
2012-12-07 15:01       ` Dietmar Maurer
2012-12-07 18:54         ` Luiz Capitulino [this message]
2012-12-08  6:26           ` Dietmar Maurer
2012-12-10 11:19             ` Luiz Capitulino
2012-12-10 12:06               ` Dietmar Maurer
2012-12-10  7:52           ` Alexandre DERUMIER

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=20121207165444.163bbb4f@doriath.home \
    --to=lcapitulino@redhat.com \
    --cc=agl@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=dietmar@proxmox.com \
    --cc=mdroth@linux.vnet.ibm.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 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).