From: Eric Blake <eblake@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] nvdimm: disable balloon
Date: Tue, 19 Jan 2016 21:59:30 -0700 [thread overview]
Message-ID: <569F1432.3060101@redhat.com> (raw)
In-Reply-To: <1453117322-30191-1-git-send-email-den@openvz.org>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
On 01/18/2016 04:42 AM, Denis V. Lunev wrote:
> From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>
> NVDIMM for now is planned to use as a backing store for DAX filesystem
> in the guest and thus this memory is excluded from guest memory management
> and LRUs.
>
> In this case libvirt running QEMU along with configured ballon almost
s/ballon/balloon/
> immediately inflates balloon and effectively kill the guest as
> qemu counts nvdimm as part of the ram.
>
> Counting dimm devices as part of the ram for ballooning was started from
> patch
> virtio-balloon: Fix balloon not working correctly when hotplug memory
Useful to mention the commit id: 463756d03
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Xiao Guangrong <guangrong.xiao@linux.intel.com>
> CC: "Michael S. Tsirkin" <mst@redhat.com>
> CC: Igor Mammedov <imammedo@redhat.com>
> CC: Eric Blake <eblake@redhat.com>
> CC: Markus Armbruster <armbru@redhat.com>
I'm just doing an interface review.
> ---
> The patch is submitted start a discussion. It may be technically correct,
> but for us the situation is a bit shady.
>
> +++ b/qapi-schema.json
> @@ -3922,6 +3922,8 @@
> #
> # @hotpluggable: true if device if could be added/removed while machine is running
> #
> +# @in-ram: true if device if should be counted in current ram size (since 2.6)
Output-only, so you are okay adding a new non-optional field. However,
is "should be counted" the right wording, or would it be better as "is
counted", given that the user doesn't have any way to change whether a
device gets counted or not, but is merely learning the state previously
chosen by the device.
As for whether it makes sense technically, I'll leave that to discussion.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2016-01-20 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 11:42 [Qemu-devel] [PATCH 1/1] nvdimm: disable balloon Denis V. Lunev
2016-01-19 8:53 ` Xiao Guangrong
2016-01-20 11:36 ` Vladimir Sementsov-Ogievskiy
2016-01-20 15:41 ` Xiao Guangrong
2016-01-25 15:24 ` Vladimir Sementsov-Ogievskiy
2016-01-20 4:59 ` 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=569F1432.3060101@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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.