From: Liang Li <liang.z.li@intel.com>
To: mst@redhat.com, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org, quintela@redhat.com,
amit.shah@redhat.com, pbonzini@redhat.com, dgilbert@redhat.com
Cc: linux-mm@kvack.org, kvm@vger.kernel.org, qemu-devel@nongnu.org,
agraf@suse.de, borntraeger@de.ibm.com,
Liang Li <liang.z.li@intel.com>
Subject: [Qemu-devel] [PATCH kernel 0/2] speed up live migration by skipping free pages
Date: Tue, 19 Apr 2016 22:34:32 +0800 [thread overview]
Message-ID: <1461076474-3864-1-git-send-email-liang.z.li@intel.com> (raw)
Current QEMU live migration implementation mark all guest's RAM pages
as dirtied in the ram bulk stage, all these pages will be processed
and it consumes quite a lot of CPU cycles and network bandwidth.
>From guest's point of view, it doesn't care about the content in free
page. We can make use of this fact and skip processing the free
pages, this can save a lot CPU cycles and reduce the network traffic
significantly while speed up the live migration process obviously.
This patch set is the kernel side implementation.
The virtio-balloon driver is extended to send the free page bitmap
from guest to QEMU.
After getting the free page bitmap, QEMU can use it to filter out
guest's free pages. This make the live migration process much more
efficient.
In order to skip more free pages, we add an interface to let the user
decide whether dropping the cache in guest during live migration.
Liang Li (2):
mm: add the related functions to build the free page bitmap
virtio-balloon: extend balloon driver to support the new feature
drivers/virtio/virtio_balloon.c | 100 ++++++++++++++++++++++++++++++++++--
fs/drop_caches.c | 22 +++++---
include/linux/fs.h | 1 +
include/uapi/linux/virtio_balloon.h | 1 +
mm/page_alloc.c | 46 +++++++++++++++++
5 files changed, 157 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-04-19 14:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:34 Liang Li [this message]
2016-04-19 14:34 ` [Qemu-devel] [PATCH kernel 1/2] mm: add the related functions to build the free page bitmap Liang Li
2016-04-19 14:54 ` Rik van Riel
2016-04-19 15:02 ` Li, Liang Z
2016-04-19 15:26 ` Rik van Riel
2016-04-20 0:57 ` Li, Liang Z
2016-04-19 16:15 ` Michael S. Tsirkin
2016-04-20 1:41 ` Li, Liang Z
2016-04-21 13:48 ` Michael S. Tsirkin
2016-04-22 1:36 ` Li, Liang Z
2016-04-22 9:48 ` Dr. David Alan Gilbert
2016-04-22 13:58 ` Michael S. Tsirkin
2016-04-25 3:11 ` Li, Liang Z
2016-04-25 10:43 ` Michael S. Tsirkin
2016-04-26 3:21 ` Li, Liang Z
2016-04-19 14:56 ` kbuild test robot
2016-04-19 16:01 ` kbuild test robot
2016-04-19 16:14 ` kbuild test robot
2016-04-19 14:34 ` [Qemu-devel] [PATCH kernel 2/2] virtio-balloon: extend balloon driver to support the new feature Liang Li
2016-04-19 16:18 ` Michael S. Tsirkin
2016-04-25 6:06 ` [Qemu-devel] [PATCH kernel 0/2] speed up live migration by skipping free pages Amit Shah
2016-04-25 11:04 ` Michael S. Tsirkin
2016-04-25 12:08 ` Amit Shah
2016-04-25 12:51 ` Michael S. Tsirkin
2016-04-25 13:17 ` 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=1461076474-3864-1-git-send-email-liang.z.li@intel.com \
--to=liang.z.li@intel.com \
--cc=agraf@suse.de \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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).