From: Eric Blake <eblake@redhat.com>
To: Chen Hanxiao <chen_han_xiao@126.com>, qemu-devel@nongnu.org
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] qga: add mountpoint usage to GuestFilesystemInfo
Date: Wed, 30 May 2018 08:08:33 -0500 [thread overview]
Message-ID: <a1533da5-308d-59c7-a0a4-863fb02d771b@redhat.com> (raw)
In-Reply-To: <20180530090121.28154-1-chen_han_xiao@126.com>
On 05/30/2018 04:01 AM, Chen Hanxiao wrote:
> From: Chen Hanxiao <chenhanxiao@gmail.com>
>
> This patch adds support for getting the usage of mounted
> filesystem.
> It's very useful when we try to monitor guest's filesystem.
>
> Cc: Michael Roth <mdroth@linux.vnet.ibm.com>
> Signed-off-by: Chen Hanxiao <chenhanxiao@gmail.com>
> ---
> v2:
> add description in qapi-schema and version numbers
> +# @usage: file system usage, integer between 0 and 100 (since 3.0)
I still find this as being too imprecise. Don't throw away data learned
from the guest that the client might like to know. Either provide a
floating point between 0 and 1, or provide the two actual statvfs()
numbers (used and total) directly and let the client perform the
division to learn the ratio.
> # @disk: an array of disk hardware information that the volume lies on,
> # which may be empty if the disk type is not supported
> #
> # Since: 2.2
> ##
> { 'struct': 'GuestFilesystemInfo',
> - 'data': {'name': 'str', 'mountpoint': 'str', 'type': 'str',
> + 'data': {'name': 'str', 'mountpoint': 'str', 'type': 'str', 'usage': 'int',
> 'disk': ['GuestDiskAddress']} }
>
> ##
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-05-30 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 9:01 [Qemu-devel] [PATCH v2] qga: add mountpoint usage to GuestFilesystemInfo Chen Hanxiao
2018-05-30 13:08 ` Eric Blake [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=a1533da5-308d-59c7-a0a4-863fb02d771b@redhat.com \
--to=eblake@redhat.com \
--cc=chen_han_xiao@126.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).