From: Paolo Bonzini <pbonzini@redhat.com>
To: vijayak@cavium.com, qemu-arm@nongnu.org, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, Prasun.Kapoor@cavium.com,
vijay.kilari@gmail.com, Suresh <ksuresh@cavium.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/1] target-arm: Use Neon for zero checking
Date: Wed, 29 Jun 2016 14:53:36 +0200 [thread overview]
Message-ID: <9b75ea7f-4b2f-4377-483e-aab3ae36a01b@redhat.com> (raw)
In-Reply-To: <1467190029-694-2-git-send-email-vijayak@cavium.com>
On 29/06/2016 10:47, vijayak@cavium.com wrote:
> From: Vijay <vijayak@cavium.com>
>
> Use Neon instructions to perform zero checking of
> buffer. This is helps in reducing total migration time.
>
> Use case: Idle VM live migration with 4 VCPUS and 8GB ram
> running CentOS 7.
>
> Without Neon, the Total migration time is 3.5 Sec
>
> Migration status: completed
> total time: 3560 milliseconds
> downtime: 33 milliseconds
> setup: 5 milliseconds
> transferred ram: 297907 kbytes
> throughput: 685.76 mbps
> remaining ram: 0 kbytes
> total ram: 8519872 kbytes
> duplicate: 2062760 pages
> skipped: 0 pages
> normal: 69808 pages
> normal bytes: 279232 kbytes
> dirty sync count: 3
>
> With Neon, the total migration time is 2.9 Sec
>
> Migration status: completed
> total time: 2960 milliseconds
> downtime: 65 milliseconds
> setup: 4 milliseconds
> transferred ram: 299869 kbytes
> throughput: 830.19 mbps
> remaining ram: 0 kbytes
> total ram: 8519872 kbytes
> duplicate: 2064313 pages
> skipped: 0 pages
> normal: 70294 pages
> normal bytes: 281176 kbytes
> dirty sync count: 3
>
> Signed-off-by: Vijaya Kumar K <vijayak@cavium.com>
> Signed-off-by: Suresh <ksuresh@cavium.com>
> ---
> util/cutils.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/util/cutils.c b/util/cutils.c
> index 5830a68..4779403 100644
> --- a/util/cutils.c
> +++ b/util/cutils.c
> @@ -184,6 +184,13 @@ int qemu_fdatasync(int fd)
> #define SPLAT(p) _mm_set1_epi8(*(p))
> #define ALL_EQ(v1, v2) (_mm_movemask_epi8(_mm_cmpeq_epi8(v1, v2)) == 0xFFFF)
> #define VEC_OR(v1, v2) (_mm_or_si128(v1, v2))
> +#elif __aarch64__
> +#include "arm_neon.h"
> +#define VECTYPE uint64x2_t
> +#define ALL_EQ(v1, v2) \
> + ((vgetq_lane_u64(v1, 0) == vgetq_lane_u64(v2, 0)) && \
> + (vgetq_lane_u64(v1, 1) == vgetq_lane_u64(v2, 1)))
> +#define VEC_OR(v1, v2) ((v1) | (v2))
> #else
> #define VECTYPE unsigned long
> #define SPLAT(p) (*(p) * (~0UL / 255))
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2016-06-29 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 8:47 [Qemu-devel] [PATCH v3 0/1] ARM64: Live migration optimization vijayak
2016-06-29 8:47 ` [Qemu-devel] [PATCH v3 1/1] target-arm: Use Neon for zero checking vijayak
2016-06-29 12:53 ` Paolo Bonzini [this message]
2016-06-30 13:45 ` Peter Maydell
2016-07-01 22:07 ` Richard Henderson
2016-07-02 9:42 ` Peter Maydell
2016-07-05 12:24 ` Vijay Kilari
2016-07-11 17:55 ` Peter Maydell
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=9b75ea7f-4b2f-4377-483e-aab3ae36a01b@redhat.com \
--to=pbonzini@redhat.com \
--cc=Prasun.Kapoor@cavium.com \
--cc=ksuresh@cavium.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vijay.kilari@gmail.com \
--cc=vijayak@cavium.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).