From: Wei Wang <wei.w.wang@intel.com>
To: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Tomáš Golembiovský" <tgolembi@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [RFC] Buffers/caches in VirtIO Balloon driver stats
Date: Tue, 29 Aug 2017 20:01:53 +0800 [thread overview]
Message-ID: <59A557B1.7080704__39112.2319423177$1504007986$gmane$org@intel.com> (raw)
In-Reply-To: <20170829095726.GL25960@stefanha-x1.localdomain>
On 08/29/2017 05:57 PM, Stefan Hajnoczi wrote:
> On Sun, Aug 27, 2017 at 11:30:33PM +0200, Tomáš Golembiovský wrote:
>> Hi,
> I have CCed the relevant mailing lists and people most recently involved
> in virtio-balloon discussions. Hopefully this will help get the right
> people to see your questions.
>
>> We'd like to include information about reclaimable memory into the
>> statistics in VirtiO Balloon driver. Namely, we'd like to include
>> counters for bufferes and caches of Linux kernel. The patch itself is
>> pretty trivial -- no problem there. But before we do that I'd like to
>> get some input from the QEMU community.
>>
>> 1) Is there any reason not to have the stats there?
Could you please share the usages of reclaimable memory via the stats?
>>
>> 2) Considering the balloon device is multiplatform (Linux, BSD,
>> Windows), is there a problem with including buffers/caches? These seem
>> to be specific to the Linux virtual memory subsystem. Of course, other
>> OSes could just report zeros. Are there some internal stats on those
>> OSes that could be filled in? I don't now if such or similar statistic
>> are available on BSD. On Windows only SystemCache stat looks like
>> something relevant. Anyone familiar with those OSes has any suggestions?
>>
>>
One of the solutions that I'm thinking about is to make virtio
platform-ware.
That is, the device by default supports
VIRTIO_F_LINUX,
VIRTIO_F_WINDOWS,
VIRTIO_F_BSD.
For the Linux driver, only VIRTIO_F_LINUX is supported, then we can
have Linux specific driver implementations under that feature.
Best,
Wei
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2017-08-29 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 21:30 [Qemu-devel] [RFC] Buffers/caches in VirtIO Balloon driver stats Tomáš Golembiovský
2017-08-29 9:57 ` Stefan Hajnoczi
2017-08-29 9:57 ` Stefan Hajnoczi
2017-08-29 12:01 ` Wei Wang [this message]
2017-08-29 12:01 ` Wei Wang
2017-08-29 12:01 ` [virtio-dev] " Wei Wang
2017-09-12 14:29 ` Tomáš Golembiovský
2017-09-12 14:29 ` Tomáš Golembiovský
2017-09-12 19:23 ` Tomáš Golembiovský
2017-09-12 19:23 ` [virtio-dev] " Tomáš Golembiovský
2017-09-12 19:23 ` Tomáš Golembiovský
2017-09-15 2:01 ` Wei Wang
2017-09-15 2:01 ` Wei Wang
2017-09-15 2:01 ` [virtio-dev] " Wei Wang
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='59A557B1.7080704__39112.2319423177$1504007986$gmane$org@intel.com' \
--to=wei.w.wang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=tgolembi@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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.