From: "Li, Liang Z" <liang.z.li@intel.com>
To: Jitendra Kolhe <jitendra.kolhe@hpe.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>
Cc: "ehabkost@redhat.com" <ehabkost@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mst@redhat.com" <mst@redhat.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"amit.shah@redhat.com" <amit.shah@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"rth@twiddle.net" <rth@twiddle.net>,
"mohan_parthasarathy@hpe.com" <mohan_parthasarathy@hpe.com>,
"simhan@hpe.com" <simhan@hpe.com>
Subject: RE: [RFC qemu 0/4] A PV solution for live migration optimization
Date: Fri, 4 Mar 2016 09:36:22 +0000 [thread overview]
Message-ID: <F2CBF3009FA73547804AE4C663CAB28E0377172C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1457083967-13681-1-git-send-email-jitendra.kolhe@hpe.com>
> > > * Liang Li (liang.z.li@intel.com) wrote:
> > > > The current QEMU live migration implementation mark the all the
> > > > guest's RAM pages as dirtied in the ram bulk stage, all these
> > > > pages will be processed and that takes quit a lot of CPU cycles.
> > > >
> > > > From guest's point of view, it doesn't care about the content in
> > > > free pages. We can make use of this fact and skip processing the
> > > > free pages in the ram bulk stage, it 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 QEMU side implementation.
> > > >
> > > > The virtio-balloon is extended so that QEMU can get the free pages
> > > > information from the guest through virtio.
> > > >
> > > > After getting the free pages information (a bitmap), QEMU can use
> > > > it to filter out the guest's free pages in the ram bulk stage.
> > > > This make the live migration process much more efficient.
> > >
> > > Hi,
> > > An interesting solution; I know a few different people have been
> > > looking at how to speed up ballooned VM migration.
> > >
> >
> > Ooh, different solutions for the same purpose, and both based on the
> balloon.
>
> We were also tying to address similar problem, without actually needing to
> modify the guest driver. Please find patch details under mail with subject.
> migration: skip sending ram pages released by virtio-balloon driver
>
> Thanks,
> - Jitendra
>
Great! Thanks for your information.
Liang
> >
> > > I wonder if it would be possible to avoid the kernel changes by
> > > parsing /proc/self/pagemap - if that can be used to detect
> > > unmapped/zero mapped pages in the guest ram, would it achieve the
> same result?
> > >
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-03-04 9:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 9:32 Jitendra Kolhe
2016-03-04 9:36 ` Li, Liang Z [this message]
2016-03-08 11:14 ` Amit Shah
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 10:44 Liang Li
2016-03-03 17:46 ` Dr. David Alan Gilbert
2016-03-04 1:52 ` Li, Liang Z
2016-03-08 11:13 ` Amit Shah
2016-03-08 13:11 ` Li, Liang Z
2016-03-10 7:44 ` Li, Liang Z
2016-03-10 7:57 ` Amit Shah
2016-03-10 8:36 ` Li, Liang Z
2016-03-10 11:18 ` Dr. David Alan Gilbert
2016-03-11 2:38 ` Li, Liang Z
2016-03-14 17:03 ` Dr. David Alan Gilbert
2016-03-15 3:31 ` Li, Liang Z
2016-03-15 10:29 ` Michael S. Tsirkin
2016-03-15 11:11 ` Li, Liang Z
2016-03-15 19:55 ` Dr. David Alan Gilbert
2016-03-16 1:20 ` Li, Liang Z
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=F2CBF3009FA73547804AE4C663CAB28E0377172C@SHSMSX101.ccr.corp.intel.com \
--to=liang.z.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jitendra.kolhe@hpe.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mohan_parthasarathy@hpe.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=simhan@hpe.com \
--cc=virtualization@lists.linux-foundation.org \
/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