From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Orit Wasserman <owasserm@redhat.com>
Subject: Re: [Qemu-devel] [RFC][PATCH 4/9] buffer_is_zero: use vector optimizations if possible
Date: Tue, 12 Mar 2013 10:09:35 -0600 [thread overview]
Message-ID: <513F533F.1010605@redhat.com> (raw)
In-Reply-To: <B3045697-71E3-4203-B575-44BC1F7E73AB@dlhnet.de>
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On 03/12/2013 10:03 AM, Peter Lieven wrote:
>>> + if (((uintptr_t) buf) % sizeof(VECTYPE) == 0
>>> + && len % 8*sizeof(VECTYPE) == 0) {
>>
>> Space around binary operators. Use CHAR_BITS instead of a magic number
>> 8.
> the 8 is not BITS_PER_BYTE or CHAR_BITS its the number of
> vectors in one loop in buffer_find_nonzero_offset(). I will add
> a constant for this to make it clearer.
Indeed, now I see it - 8 is the unroll factor. Well, all the more
evidence that a named constant makes the code easier to read, compared
to me mis-interpreting the magic number.
--
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: 621 bytes --]
prev parent reply other threads:[~2013-03-12 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:50 [Qemu-devel] [RFC][PATCH 4/9] buffer_is_zero: use vector optimizations if possible Peter Lieven
2013-03-12 16:01 ` Eric Blake
2013-03-12 16:03 ` Peter Lieven
2013-03-12 16:09 ` Eric Blake [this message]
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=513F533F.1010605@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@dlhnet.de \
--cc=qemu-devel@nongnu.org \
--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 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.