qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlhnet.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Orit Wasserman <owasserm@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: [Qemu-devel] [RFC][PATCH 0/9] live migration/buffer_is_zero optimizations
Date: Tue, 12 Mar 2013 16:47:18 +0100	[thread overview]
Message-ID: <513F4E06.6070409@dlhnet.de> (raw)

I will sent a list of optimizations that have been developed during
the last days. Your feedback is much appreciated.

@Paolo: Can you run your tests that you have made for your migration
optimzations that are now upstream against these patches.

Thanks,
Peter

Peter Lieven (9):
   move vector definitions to qemu-common.h
   add a function to find non-zero content in a buffer
   migration: add an indicator for bulk state of ram migration
   buffer_is_zero: use vector optimizations if possible
   migration: check for dup pages only in bulk stage
   migration: use XBZRLE only after bulk stage
   bitops: use vector algorithm to optimize find_next_bit()
   migration: do not send zero_pages in bulk stage
   migration: do not search dirty pages in bulk stage

  arch_init.c           |   43 +++++++++++++++++--------------------------
  include/qemu-common.h |   24 ++++++++++++++++++++++++
  util/bitops.c         |   23 ++++++++++++++++++++---
  util/cutils.c         |   35 +++++++++++++++++++++++++++++++++++
  4 files changed, 96 insertions(+), 29 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2013-03-12 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 15:47 Peter Lieven [this message]
2013-03-12 15:56 ` [Qemu-devel] [RFC][PATCH 0/9] live migration/buffer_is_zero optimizations Eric Blake
2013-03-12 16:08   ` Peter Lieven
2013-03-12 16:11 ` Markus Armbruster

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=513F4E06.6070409@dlhnet.de \
    --to=pl@dlhnet.de \
    --cc=kwolf@redhat.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 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).