From: David Hildenbrand <david@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, mst@redhat.com
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 2/2] virtio-balloon: Restore MADV_WILLNEED hint on balloon deflate
Date: Tue, 5 Mar 2019 15:15:38 +0100 [thread overview]
Message-ID: <00e325d4-b23c-7239-46e6-a55fd1f9d5f4@redhat.com> (raw)
In-Reply-To: <20190305051134.27930-3-david@gibson.dropbear.id.au>
On 05.03.19 06:11, David Gibson wrote:
> Prior to f6deb6d9 "virtio-balloon: Remove unnecessary MADV_WILLNEED on
> deflate", the balloon device issued an madvise() MADV_WILLNEED on
> pages removed from the balloon. That would hint to the host kernel
> that the pages were likely to be needed by the guest in the near
> future.
>
> It's unclear if this is actually valuable or not, and so f6deb6d9
> removed this, essentially ignoring balloon deflate requests. However,
> concerns have been raised that this might cause a performance
> regression by causing extra latency for the guest in certain
> configurations.
I mean, it will mainly create page tables as far as I know. Any write to
a page will have an overhead either way (COW zero page). Reads *might*
be faster.
As we are working on 4k granularity in the balloon (and doing
MADV_DONTNEED on 4k granularity!), there will most probably be page
tables already either way. A page table could only be zapped if all
pages of that page table are MADV_DONTNEED'ed (or I assume never were
touched), and I am not sure if "random MADV_DONTNEED'ing of 4k pages"
will actually get rid of page tables (my assumption would be: only if a
complete range is zapped at once). I haven't looked into the details,
though (plenty of other stuff to do).
I am not sure if I share the concerns. Real-time workload should never
use the virtio-balloon in a way that anything like that would be possible.
>
> So, until we can get actual benchmark data to see if that's the case,
> this restores (by default) the old behaviour, issuing a MADV_WILLNEED
> when a page is removed from the balloon. A new property on the
> balloon device "hint-on-deflate" can be set to false to remove this
> behaviour for testing.
This is certainly a good approach for you to finally be able to leave
the ugly land of virtio-balloon :)
But at least to me, this looks completely useless. I'll be happy to be
proven wrong as always :)
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> hw/virtio/virtio-balloon.c | 15 +++++++++++++++
> include/hw/virtio/virtio-balloon.h | 1 +
> 2 files changed, 16 insertions(+)
>
> diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
> index e5e82b556d..69968502d9 100644
> --- a/hw/virtio/virtio-balloon.c
> +++ b/hw/virtio/virtio-balloon.c
> @@ -146,6 +146,20 @@ static void balloon_deflate_page(VirtIOBalloon *balloon,
> balloon->pbp = NULL;
> }
> }
> +
> + if (balloon->hint_on_deflate) {
> + void *host_addr = (void *)((uintptr_t)addr & ~(rb_page_size - 1));
> + int ret;
> +
> + /* When a page is deflated, we hint the whole host page it
> + * lives on, since we can't do anything smaller */
> + ret = qemu_madvise(host_addr, rb_page_size, QEMU_MADV_WILLNEED);
> + if (ret != 0) {
> + warn_report("Couldn't MADV_WILLNEED on balloon deflate: %s",
> + strerror(errno));
> + /* Otherwise ignore, failing to page hint shouldn't be fatal */
> + }
> + }
> }
>
> static const char *balloon_stat_names[] = {
> @@ -622,6 +636,7 @@ static const VMStateDescription vmstate_virtio_balloon = {
> static Property virtio_balloon_properties[] = {
> DEFINE_PROP_BIT("deflate-on-oom", VirtIOBalloon, host_features,
> VIRTIO_BALLOON_F_DEFLATE_ON_OOM, false),
> + DEFINE_PROP_BOOL("hint-on-deflate", VirtIOBalloon, hint_on_deflate, true),
> DEFINE_PROP_END_OF_LIST(),
> };
>
> diff --git a/include/hw/virtio/virtio-balloon.h b/include/hw/virtio/virtio-balloon.h
> index 99dcd6d105..69732cedaa 100644
> --- a/include/hw/virtio/virtio-balloon.h
> +++ b/include/hw/virtio/virtio-balloon.h
> @@ -45,6 +45,7 @@ typedef struct VirtIOBalloon {
> int64_t stats_poll_interval;
> uint32_t host_features;
> PartiallyBalloonedPage *pbp;
> + bool hint_on_deflate;
> } VirtIOBalloon;
>
> #endif
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-03-05 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 5:11 [Qemu-devel] [RFC 0/2] virtio-balloon: Some further fixes David Gibson
2019-03-05 5:11 ` [Qemu-devel] [RFC 1/2] virtio-balloon: Fix possible guest memory corruption with inflates & deflates David Gibson
2019-03-05 5:11 ` [Qemu-devel] [RFC 2/2] virtio-balloon: Restore MADV_WILLNEED hint on balloon deflate David Gibson
2019-03-05 14:15 ` David Hildenbrand [this message]
2019-03-05 16:03 ` Michael S. Tsirkin
2019-03-05 16:10 ` David Hildenbrand
2019-03-05 17:02 ` Michael S. Tsirkin
2019-03-05 23:42 ` David Gibson
2019-03-05 23:40 ` David Gibson
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=00e325d4-b23c-7239-46e6-a55fd1f9d5f4@redhat.com \
--to=david@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).