From: Eric Blake <eblake@redhat.com>
To: 陈梁 <chenliang0016@icloud.com>
Cc: ChenLiang <chenliang88@huawei.com>,
weidong.huang@huawei.com, quintela@redhat.com,
qemu-devel@nongnu.org, dgilbert@redhat.com, owasserm@redhat.com,
arei.gonglei@huawei.com, mrhines@us.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] xbzrle: don't check the value in the vm ram repeatedly
Date: Sat, 29 Mar 2014 09:38:32 -0600 [thread overview]
Message-ID: <5336E8F8.5040107@redhat.com> (raw)
In-Reply-To: <F5241465-1514-4695-8EE0-F781549403FF@icloud.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On 03/29/2014 09:12 AM, 陈梁 wrote:
> /* word at a time for speed */
> if (!res) {
> while (i < slen &&
> (*(long *)(old_buf + i)) == (*(long *)(new_buf + i))) {
> i += sizeof(long);
> zrun_len += sizeof(long);
> }
>
> /* go over the rest */
> //while (i < slen && old_buf[i] == new_buf[i]) {
> // zrun_len++;
> // i++;
> //}
> }
> i += sizeof(long);
> nzrun_len += sizeof(long);
That does not produce a minimal compression (it treats all 8 bytes as
different, even if 7 of them were the same). It might be a viable
solution if the extra overhead of the additional bytes sent over the
wire is less than the overhead saved by not re-checking the temporary
variable to determine a better compression. But I'm not convinced - it
seems that reading memory into a register, then doing multiple
operations on that cached value, will be a win (that is, minimal
compression matters, because time spent transmitting bytes over the
network is slower than time spent calculating how to avoid bytes to
transmit).
--
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 --]
next prev parent reply other threads:[~2014-03-29 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 7:52 [Qemu-devel] [PATCH] xbzrle: don't check the value in the vm ram repeatedly arei.gonglei
2014-03-29 13:53 ` Eric Blake
2014-03-29 14:15 ` 陈梁
2014-03-29 14:26 ` Eric Blake
[not found] ` <C734EB68-7CC7-4028-BD08-0FC54819FD21@icloud.com>
[not found] ` <F822EA2B-2483-446F-A92C-662B381D1B81@icloud.com>
2014-03-29 15:33 ` Eric Blake
[not found] ` <F5241465-1514-4695-8EE0-F781549403FF@icloud.com>
2014-03-29 15:38 ` Eric Blake [this message]
2014-03-31 9:40 ` 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=5336E8F8.5040107@redhat.com \
--to=eblake@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=chenliang0016@icloud.com \
--cc=chenliang88@huawei.com \
--cc=dgilbert@redhat.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=weidong.huang@huawei.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).