qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Orit Wasserman <owasserm@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
	anthony@codemonkey.ws, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/6] XBZRLE cache size should not be larger than guest memory size
Date: Thu, 30 Jan 2014 18:48:24 +0000	[thread overview]
Message-ID: <20140130184823.GJ2655@work-vm> (raw)
In-Reply-To: <52EA9D1B.1090305@redhat.com>

* Orit Wasserman (owasserm@redhat.com) wrote:
> On 01/30/2014 08:23 PM, Dr. David Alan Gilbert wrote:
> >* Orit Wasserman (owasserm@redhat.com) wrote:
> >>Signed-off-by: Orit Wasserman <owasserm@redhat.com>
> >>---
> >>  migration.c | 7 +++++++
> >>  1 file changed, 7 insertions(+)
> >>
> >>diff --git a/migration.c b/migration.c
> >>index 46a7305..25add6f 100644
> >>--- a/migration.c
> >>+++ b/migration.c
> >>@@ -479,6 +479,13 @@ void qmp_migrate_set_cache_size(int64_t value, Error **errp)
> >>          return;
> >>      }
> >>
> >>+    /* Cache should not be larger than guest ram size */
> >
> >Why? (It's admittedly odd, but does it actually break something if it's larger?)
> >
> 
> Because how XBZRLE works, the idea is that for workload that changes the same pages
> frequently, we can reduce the amount of transferred data sent by sending only the diff.
> We also compress the diff itself.
>
> The cache is used to store the previous page so we can calculate the diff, so at most it will
> contain all the guest pages.

It's a hash based cache though isn't it - so there will be some contention for
a cache size==ram size case?

Also this does mean that you have to be a little careful to pick a sane XBZRLE cache
size, since one that's too large will now fail; I can only see that being
a problem on a machine with a mix of huge and tiny VMs.

( I sent the reviewd-by tag separately.)

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2014-01-30 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 18:08 [Qemu-devel] [PATCH v2 0/6] XBZRLE Fixes Orit Wasserman
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 1/6] Set xbzrle buffers to NULL after freeing them to avoid double free errors Orit Wasserman
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 2/6] Add check for cache size smaller than page size Orit Wasserman
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 3/6] migration:fix free XBZRLE decoded_buf wrong Orit Wasserman
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 4/6] XBZRLE cache size should not be larger than guest memory size Orit Wasserman
2014-01-30 18:23   ` Dr. David Alan Gilbert
2014-01-30 18:42     ` Orit Wasserman
2014-01-30 18:48       ` Dr. David Alan Gilbert [this message]
2014-01-30 18:59         ` Orit Wasserman
2014-01-30 18:45   ` Dr. David Alan Gilbert
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 5/6] Don't abort on out of memory when creating page cache Orit Wasserman
2014-01-30 18:21   ` Dr. David Alan Gilbert
2014-01-30 18:08 ` [Qemu-devel] [PATCH v2 6/6] Don't abort on memory allocation error Orit Wasserman
2014-01-30 18:17   ` Dr. David Alan Gilbert

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=20140130184823.GJ2655@work-vm \
    --to=dgilbert@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=owasserm@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 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).