From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Wei Yang <richard.weiyang@huawei.com>
Cc: "Li, Liang Z" <liang.z.li@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kenel.org" <linux-kernel@vger.kenel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"amit.shah@redhat.com" <amit.shah@redhat.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"mohan_parthasarathy@hpe.com" <mohan_parthasarathy@hpe.com>,
"jitendra.kolhe@hpe.com" <jitendra.kolhe@hpe.com>,
"simhan@hpe.com" <simhan@hpe.com>,
"rkagan@virtuozzo.com" <rkagan@virtuozzo.com>,
"riel@redhat.com" <riel@redhat.com>
Subject: Re: [RFC Design Doc]Speed up live migration by skipping free pages
Date: Thu, 24 Mar 2016 09:00:05 +0000 [thread overview]
Message-ID: <20160324090004.GA2230@work-vm> (raw)
In-Reply-To: <20160324012424.GB14956@linux-gk3p>
* Wei Yang (richard.weiyang@huawei.com) wrote:
> On Wed, Mar 23, 2016 at 06:48:22AM +0000, Li, Liang Z wrote:
> [...]
> >> > 8. Pseudo code
> >> > Dirty page logging should be enabled before getting the free page
> >> > information from guest, this is important because during the process
> >> > of getting free pages, some free pages may be used and written by the
> >> > guest, dirty page logging can trace these pages. The pseudo code is
> >> > like below:
> >> >
> >> > -----------------------------------------------
> >> > MigrationState *s = migrate_get_current();
> >> > ...
> >> >
> >> > memory_global_dirty_log_start();
> >> >
> >> > if (get_guest_mem_info(&info)) {
> >> > while (!get_free_page_bmap(free_page_bitmap, drop_page_cache)
> >> &&
> >> > s->state != MIGRATION_STATUS_CANCELLING) {
> >> > usleep(1000) // sleep for 1 ms
> >> > }
> >> >
> >> > tighten_free_page_bmap =
> >> tighten_guest_free_pages(free_page_bitmap);
> >> > filter_out_guest_free_pages(tighten_free_page_bmap);
> >> > }
> >>
> >> Given the typical speed of networks; it wouldn't do too much harm to start
> >> sending assuming all pages are dirty and then when the guest finally gets
> >> around to finishing the bitmap then update, so it's asynchronous - and then if
> >> the guest never responds we don't really care.
> >
> >Indeed, thanks!
> >
>
> This is interesting. By doing so, the threshold I mentioned in another mail is
> not necessary, since we can do it in parallel.
Actually I just realised it's a little more complex; we can't sync the dirty
bitmap again from the guest until after we've received the guests 'free' bitmap;
that's because we wouldn't know if a 'dirty' page reflected that a page declared
as 'free' had now been reused - so there is still an ordering there.
Dave
>
> >Liang
> >>
> >> Dave
> >>
> >> >
> >> > migration_bitmap_sync();
> >> > ...
> >> >
> >> > -----------------------------------------------
> >> >
> >> >
> >> > --
> >> > 1.9.1
> >> >
> >> --
> >> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >N�����r��y���b�X��ǧv�^�){.n�+����h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[f
> --
> Richard Yang\nHelp you, Help me
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
WARNING: multiple messages have this Message-ID (diff)
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Wei Yang <richard.weiyang@huawei.com>
Cc: "rkagan@virtuozzo.com" <rkagan@virtuozzo.com>,
"linux-kernel@vger.kenel.org" <linux-kernel@vger.kenel.org>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mst@redhat.com" <mst@redhat.com>,
"simhan@hpe.com" <simhan@hpe.com>,
"Li, Liang Z" <liang.z.li@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jitendra.kolhe@hpe.com" <jitendra.kolhe@hpe.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"mohan_parthasarathy@hpe.com" <mohan_parthasarathy@hpe.com>,
"amit.shah@redhat.com" <amit.shah@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC Design Doc]Speed up live migration by skipping free pages
Date: Thu, 24 Mar 2016 09:00:05 +0000 [thread overview]
Message-ID: <20160324090004.GA2230@work-vm> (raw)
In-Reply-To: <20160324012424.GB14956@linux-gk3p>
* Wei Yang (richard.weiyang@huawei.com) wrote:
> On Wed, Mar 23, 2016 at 06:48:22AM +0000, Li, Liang Z wrote:
> [...]
> >> > 8. Pseudo code
> >> > Dirty page logging should be enabled before getting the free page
> >> > information from guest, this is important because during the process
> >> > of getting free pages, some free pages may be used and written by the
> >> > guest, dirty page logging can trace these pages. The pseudo code is
> >> > like below:
> >> >
> >> > -----------------------------------------------
> >> > MigrationState *s = migrate_get_current();
> >> > ...
> >> >
> >> > memory_global_dirty_log_start();
> >> >
> >> > if (get_guest_mem_info(&info)) {
> >> > while (!get_free_page_bmap(free_page_bitmap, drop_page_cache)
> >> &&
> >> > s->state != MIGRATION_STATUS_CANCELLING) {
> >> > usleep(1000) // sleep for 1 ms
> >> > }
> >> >
> >> > tighten_free_page_bmap =
> >> tighten_guest_free_pages(free_page_bitmap);
> >> > filter_out_guest_free_pages(tighten_free_page_bmap);
> >> > }
> >>
> >> Given the typical speed of networks; it wouldn't do too much harm to start
> >> sending assuming all pages are dirty and then when the guest finally gets
> >> around to finishing the bitmap then update, so it's asynchronous - and then if
> >> the guest never responds we don't really care.
> >
> >Indeed, thanks!
> >
>
> This is interesting. By doing so, the threshold I mentioned in another mail is
> not necessary, since we can do it in parallel.
Actually I just realised it's a little more complex; we can't sync the dirty
bitmap again from the guest until after we've received the guests 'free' bitmap;
that's because we wouldn't know if a 'dirty' page reflected that a page declared
as 'free' had now been reused - so there is still an ordering there.
Dave
>
> >Liang
> >>
> >> Dave
> >>
> >> >
> >> > migration_bitmap_sync();
> >> > ...
> >> >
> >> > -----------------------------------------------
> >> >
> >> >
> >> > --
> >> > 1.9.1
> >> >
> >> --
> >> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >N�����r��y���b�X��ǧv�^�){.n�+����h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[f
> --
> Richard Yang\nHelp you, Help me
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-03-24 9:00 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:43 [RFC Design Doc]Speed up live migration by skipping free pages Liang Li
2016-03-22 7:43 ` [Qemu-devel] " Liang Li
2016-03-22 10:11 ` Michael S. Tsirkin
2016-03-22 10:11 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-23 6:05 ` Li, Liang Z
2016-03-23 6:05 ` [Qemu-devel] " Li, Liang Z
2016-03-23 14:08 ` Michael S. Tsirkin
2016-03-23 14:08 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 1:19 ` Li, Liang Z
2016-03-24 1:19 ` [Qemu-devel] " Li, Liang Z
2016-03-24 9:48 ` Michael S. Tsirkin
2016-03-24 9:48 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 10:16 ` Li, Liang Z
2016-03-24 10:16 ` [Qemu-devel] " Li, Liang Z
2016-03-24 10:29 ` Michael S. Tsirkin
2016-03-24 10:29 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 14:33 ` Li, Liang Z
2016-03-24 14:33 ` [Qemu-devel] " Li, Liang Z
2016-03-24 14:44 ` Michael S. Tsirkin
2016-03-24 14:44 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 15:16 ` Li, Liang Z
2016-03-24 15:16 ` [Qemu-devel] " Li, Liang Z
2016-03-24 15:18 ` Paolo Bonzini
2016-03-24 15:18 ` [Qemu-devel] " Paolo Bonzini
2016-03-24 15:25 ` Li, Liang Z
2016-03-24 15:25 ` [Qemu-devel] " Li, Liang Z
2016-03-24 15:27 ` Michael S. Tsirkin
2016-03-24 15:27 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 15:39 ` Li, Liang Z
2016-03-24 15:39 ` [Qemu-devel] " Li, Liang Z
2016-03-24 15:47 ` Paolo Bonzini
2016-03-24 15:47 ` [Qemu-devel] " Paolo Bonzini
2016-03-24 15:59 ` Li, Liang Z
2016-03-24 15:59 ` [Qemu-devel] " Li, Liang Z
2016-03-22 19:05 ` Dr. David Alan Gilbert
2016-03-22 19:05 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-03-23 6:48 ` Li, Liang Z
2016-03-23 6:48 ` [Qemu-devel] " Li, Liang Z
2016-03-24 1:24 ` Wei Yang
2016-03-24 1:24 ` [Qemu-devel] " Wei Yang
2016-03-24 9:00 ` Dr. David Alan Gilbert [this message]
2016-03-24 9:00 ` Dr. David Alan Gilbert
2016-03-24 10:09 ` Li, Liang Z
2016-03-24 10:09 ` [Qemu-devel] " Li, Liang Z
2016-03-24 10:23 ` Dr. David Alan Gilbert
2016-03-24 10:23 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-03-24 14:50 ` Li, Liang Z
2016-03-24 14:50 ` [Qemu-devel] " Li, Liang Z
2016-03-24 15:11 ` Michael S. Tsirkin
2016-03-24 15:11 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 15:53 ` Li, Liang Z
2016-03-24 15:53 ` [Qemu-devel] " Li, Liang Z
2016-03-24 15:56 ` Michael S. Tsirkin
2016-03-24 15:56 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 16:05 ` Li, Liang Z
2016-03-24 16:05 ` [Qemu-devel] " Li, Liang Z
2016-03-24 16:25 ` Michael S. Tsirkin
2016-03-24 16:25 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-24 17:49 ` Dr. David Alan Gilbert
2016-03-24 17:49 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-03-24 22:16 ` Michael S. Tsirkin
2016-03-24 22:16 ` [Qemu-devel] " Michael S. Tsirkin
2016-03-25 1:59 ` Li, Liang Z
2016-03-25 1:59 ` [Qemu-devel] " Li, Liang Z
2016-03-25 1:32 ` Li, Liang Z
2016-03-25 1:32 ` [Qemu-devel] " Li, Liang Z
2016-04-18 11:08 ` Li, Liang Z
2016-04-18 11:08 ` [Qemu-devel] " Li, Liang Z
2016-04-18 11:29 ` Michael S. Tsirkin
2016-04-18 11:29 ` [Qemu-devel] " Michael S. Tsirkin
2016-04-18 14:36 ` Li, Liang Z
2016-04-18 14:36 ` [Qemu-devel] " Li, Liang Z
2016-04-18 15:38 ` Michael S. Tsirkin
2016-04-18 15:38 ` [Qemu-devel] " Michael S. Tsirkin
2016-04-19 2:20 ` Li, Liang Z
2016-04-19 2:20 ` [Qemu-devel] " Li, Liang Z
2016-04-19 19:12 ` Dr. David Alan Gilbert
2016-04-19 19:12 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-25 10:56 ` Michael S. Tsirkin
2016-04-25 10:56 ` [Qemu-devel] " Michael S. Tsirkin
2016-04-19 19:05 ` Dr. David Alan Gilbert
2016-04-19 19:05 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-20 3:22 ` Li, Liang Z
2016-04-20 3:22 ` [Qemu-devel] " Li, Liang Z
2016-04-20 8:10 ` Dr. David Alan Gilbert
2016-04-20 8:10 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-03-25 1:32 ` Li, Liang Z
2016-03-25 1:32 ` [Qemu-devel] " Li, Liang Z
2016-04-01 10:54 ` Amit Shah
2016-04-01 10:54 ` [Qemu-devel] " Amit Shah
2016-04-05 1:49 ` Li, Liang Z
2016-04-05 1:49 ` [Qemu-devel] " Li, Liang Z
2016-03-23 1:37 ` Wei Yang
2016-03-23 1:37 ` [Qemu-devel] " Wei Yang
2016-03-23 7:18 ` Li, Liang Z
2016-03-23 7:18 ` [Qemu-devel] " Li, Liang Z
2016-03-23 9:46 ` Wei Yang
2016-03-23 9:46 ` [Qemu-devel] " Wei Yang
2016-03-23 14:35 ` Li, Liang Z
2016-03-23 14:35 ` [Qemu-devel] " Li, Liang Z
2016-03-24 0:52 ` Wei Yang
2016-03-24 0:52 ` [Qemu-devel] " Wei Yang
2016-03-24 1:32 ` Li, Liang Z
2016-03-24 1:32 ` [Qemu-devel] " Li, Liang Z
2016-03-24 1:56 ` Wei Yang
2016-03-24 1:56 ` [Qemu-devel] " Wei Yang
2016-03-23 16:53 ` Eric Blake
2016-03-23 16:53 ` Eric Blake
2016-03-23 21:41 ` Wei Yang
2016-03-23 21:41 ` Wei Yang
2016-03-24 1:23 ` Li, Liang Z
2016-03-24 1:23 ` 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=20160324090004.GA2230@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@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.kenel.org \
--cc=mohan_parthasarathy@hpe.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.weiyang@huawei.com \
--cc=riel@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
--cc=simhan@hpe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.