From: Juan Quintela <quintela@redhat.com>
To: Yang Hongyang <yanghongyang@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Huangzhichao <huangzhichao@huawei.com>,
wangxinxin.wang@huawei.com, pbonzini@redhat.com,
"Gonglei (Arei)" <arei.gonglei@huawei.com>
Subject: Re: [Qemu-devel] About QEMU BQL and dirty log switch in Migration
Date: Mon, 24 Apr 2017 14:06:11 +0200 [thread overview]
Message-ID: <874lxeovrg.fsf@secure.mitica> (raw)
In-Reply-To: <830bfc39-56c7-a901-9ebb-77d6e7a5614c@huawei.com> (Yang Hongyang's message of "Mon, 24 Apr 2017 19:46:19 +0800")
Yang Hongyang <yanghongyang@huawei.com> wrote:
> Hi all,
>
> We found dirty log switch costs more then 13 seconds while migrating
> a 4T memory guest, and dirty log switch is currently protected by QEMU
> BQL. This causes guest freeze for a long time when switching dirty log on,
> and the migration downtime is unacceptable.
> Are there any chance to optimize the time cost for dirty log switch operation?
> Or move the time consuming operation out of the QEMU BQL?
Hi
Could you specify what do you mean by dirty log switch?
The one inside kvm?
The merge between kvm one and migration bitmap?
Thanks, Juan.
next prev parent reply other threads:[~2017-04-24 12:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 11:46 [Qemu-devel] About QEMU BQL and dirty log switch in Migration Yang Hongyang
2017-04-24 12:06 ` Juan Quintela [this message]
2017-04-24 12:13 ` Yang Hongyang
2017-04-24 16:42 ` Dr. David Alan Gilbert
2017-04-26 15:46 ` Paolo Bonzini
2017-04-27 2:46 ` Yang Hongyang
2017-05-11 12:07 ` Zhoujian (jay)
2017-05-11 12:24 ` Paolo Bonzini
2017-05-11 13:43 ` Wanpeng Li
2017-05-11 13:49 ` Wanpeng Li
2017-05-11 14:18 ` Zhoujian (jay)
2017-05-12 6:34 ` Wanpeng Li
2017-05-17 2:20 ` Zhoujian (jay)
2017-05-17 5:47 ` Wanpeng Li
2017-05-17 7:35 ` Jay Zhou
2017-05-17 7:43 ` Paolo Bonzini
2017-05-17 8:38 ` Wanpeng Li
2017-05-19 8:09 ` Jay Zhou
2017-05-19 8:32 ` Xiao Guangrong
2017-05-19 9:27 ` Jay Zhou
2018-12-11 3:43 ` Wanpeng Li
2017-05-12 8:09 ` Xiao Guangrong
2017-05-12 8:42 ` Hailiang Zhang
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=874lxeovrg.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangxinxin.wang@huawei.com \
--cc=yanghongyang@huawei.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).