From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: quintela@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
Peter Lieven <pl@kamp.de>, Orit Wasserman <owasserm@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCHv5 04/10] buffer_is_zero: use vector optimizations if possible
Date: Tue, 26 Mar 2013 10:58:33 +0100 [thread overview]
Message-ID: <1364291919-19563-5-git-send-email-pl@kamp.de> (raw)
In-Reply-To: <1364291919-19563-1-git-send-email-pl@kamp.de>
performance gain on SSE2 is approx. 20-25%. altivec
is not tested. performance for unsigned long arithmetic
is unchanged.
Signed-off-by: Peter Lieven <pl@kamp.de>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Orit Wasserman <owasserm@redhat.com>
---
util/cutils.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/util/cutils.c b/util/cutils.c
index 0314a18..daf032a 100644
--- a/util/cutils.c
+++ b/util/cutils.c
@@ -215,6 +215,11 @@ bool buffer_is_zero(const void *buf, size_t len)
long d0, d1, d2, d3;
const long * const data = buf;
+ /* use vector optimized zero check if possible */
+ if (can_use_buffer_find_nonzero_offset(buf, len)) {
+ return buffer_find_nonzero_offset(buf, len) == len;
+ }
+
assert(len % (4 * sizeof(long)) == 0);
len /= sizeof(long);
--
1.7.9.5
next prev parent reply other threads:[~2013-03-26 10:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 9:58 [Qemu-devel] [PATCHv5 00/10] buffer_is_zero / migration optimizations Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 01/10] move vector definitions to qemu-common.h Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 02/10] add a zero splat vector " Peter Lieven
2013-03-26 10:14 ` Paolo Bonzini
2013-03-26 10:17 ` Peter Lieven
2013-03-26 10:17 ` Paolo Bonzini
2013-03-26 10:18 ` Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 03/10] cutils: add a function to find non-zero content in a buffer Peter Lieven
2013-03-26 10:38 ` Juan Quintela
2013-03-26 10:42 ` Peter Lieven
2013-03-26 10:41 ` Juan Quintela
2013-03-26 9:58 ` Peter Lieven [this message]
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 05/10] bitops: unroll while loop in find_next_bit() Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 06/10] migration: search for zero instead of dup pages Peter Lieven
2013-04-05 19:23 ` Kevin Wolf
2013-04-05 20:00 ` Paolo Bonzini
2013-04-05 21:44 ` Peter Lieven
2013-04-05 22:06 ` Peter Lieven
2013-04-08 8:38 ` Paolo Bonzini
2013-04-08 9:25 ` Peter Lieven
2013-04-08 10:33 ` Paolo Bonzini
2013-04-08 8:33 ` Peter Lieven
2013-04-08 8:39 ` Peter Lieven
2013-04-08 8:49 ` Kevin Wolf
2013-04-08 8:50 ` Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 07/10] migration: add an indicator for bulk state of ram migration Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 08/10] migration: do not sent zero pages in bulk stage Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 09/10] migration: do not search dirty " Peter Lieven
2013-03-26 9:58 ` [Qemu-devel] [PATCHv5 10/10] migration: use XBZRLE only after " Peter Lieven
2013-03-26 10:46 ` [Qemu-devel] [PATCHv5 00/10] buffer_is_zero / migration optimizations Juan Quintela
2013-03-26 11:02 ` Peter Lieven
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=1364291919-19563-5-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).