All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, owasserm@redhat.com
Subject: Re: [Qemu-devel] [PATCH] docs/xbzrle: correction
Date: Mon, 26 Sep 2016 18:19:18 +0800	[thread overview]
Message-ID: <57E8F626.8020505@cn.fujitsu.com> (raw)
In-Reply-To: <1473333238-3307-1-git-send-email-caoj.fnst@cn.fujitsu.com>

ping

On 09/08/2016 07:13 PM, Cao jin wrote:
> 1. Default cache size is 64MB.
> 2. Semantics correction.
>
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
>   docs/xbzrle.txt | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/xbzrle.txt b/docs/xbzrle.txt
> index 52c8511..c0a7dfd 100644
> --- a/docs/xbzrle.txt
> +++ b/docs/xbzrle.txt
> @@ -42,7 +42,7 @@ nzrun = length byte...
>   length = uleb128 encoded integer
>
>   On the sender side XBZRLE is used as a compact delta encoding of page updates,
> -retrieving the old page content from the cache (default size of 512 MB). The
> +retrieving the old page content from the cache (default size of 64MB). The
>   receiving side uses the existing page's content and XBZRLE to decode the new
>   page's content.
>
> @@ -73,7 +73,7 @@ e9 07 0f 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 03 01 67 01 01 69
>
>   Cache update strategy
>   =====================
> -Keeping the hot pages in the cache is effective for decreased cache
> +Keeping the hot pages in the cache is effective for decreasing cache
>   misses. XBZRLE uses a counter as the age of each page. The counter will
>   increase after each ram dirty bitmap sync. When a cache conflict is
>   detected, XBZRLE will only evict pages in the cache that are older than
>

-- 
Yours Sincerely,

Cao jin

  reply	other threads:[~2016-09-26 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 11:13 [Qemu-devel] [PATCH] docs/xbzrle: correction Cao jin
2016-09-26 10:19 ` Cao jin [this message]
2016-10-05 11:13 ` Juan Quintela

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=57E8F626.8020505@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=amit.shah@redhat.com \
    --cc=owasserm@redhat.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 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.