From: Amit Shah <amit.shah@redhat.com>
To: Jitendra Kolhe <jitendra.kolhe@hpe.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, quintela@redhat.com,
qemu-devel@nongnu.org, liang.z.li@intel.com, dgilbert@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, mst@redhat.com,
mohan_parthasarathy@hpe.com, simhan@hpe.com, pbonzini@redhat.com,
akpm@linux-foundation.org,
virtualization@lists.linux-foundation.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC kernel 0/2]A PV solution for KVM live migration optimization
Date: Thu, 10 Mar 2016 13:00:00 +0530 [thread overview]
Message-ID: <20160310073000.GA4678@grmbl.mre> (raw)
In-Reply-To: <1457593292-30686-1-git-send-email-jitendra.kolhe@hpe.com>
On (Thu) 10 Mar 2016 [12:31:32], Jitendra Kolhe wrote:
> On 3/8/2016 4:44 PM, Amit Shah wrote:
> >>>> 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
> >
> > The scope of this patch series seems to be wider: don't send free
> > pages to a dest at all, vs. don't send pages that are ballooned out.
>
> Hi,
>
> Thanks for your response. The scope of this patch series doesn’t seem to take care
> of ballooned out pages. To balloon out a guest ram page the guest balloon driver does
> a alloc_page() and then return the guest pfn to Qemu, so ballooned out pages will not
> be seen as free ram pages by the guest.
> Thus we will still end up scanning (for zero page) for ballooned out pages during
> migration. It would be ideal if we could have both solutions.
Yes, of course it would be nice to have both solutions. My response was to the line:
> >>> Ooh, different solutions for the same purpose, and both based on the balloon.
which sounded misleading to me for a couple of reasons: 1, as you
describe, pages being considered by this patchset and yours are
different; and 2, as I mentioned in the other mail, this patchset
doesn't really depend on the balloon, and I believe it should not.
Amit
next prev parent reply other threads:[~2016-03-10 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 7:01 [Qemu-devel] [RFC kernel 0/2]A PV solution for KVM live migration optimization Jitendra Kolhe
2016-03-10 7:22 ` Li, Liang Z
2016-03-10 7:30 ` Amit Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 10:46 Liang Li
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=20160310073000.GA4678@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jitendra.kolhe@hpe.com \
--cc=kvm@vger.kernel.org \
--cc=liang.z.li@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).