From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Avi Kivity <avi@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
quintela@redhat.com, Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] KVM: Dirty logging optimization using rmap
Date: Wed, 30 Nov 2011 14:15:47 +0900 [thread overview]
Message-ID: <4ED5BC03.5000901@oss.ntt.co.jp> (raw)
In-Reply-To: <4ED5B8F2.2090804@oss.ntt.co.jp>
(2011/11/30 14:02), Takuya Yoshikawa wrote:
> IIUC, even though O(1) is O(1) at the timing of GET DIRTY LOG, it needs O(N) write
> protections with respect to the total number of dirty pages: distributed, but
> actually each page fault, which should be logged, does some write protection?
Sorry, was not precise. It depends on the level, and not completely distributed.
But I think it is O(N), and the total number of costs will not change so much,
I guess.
Takuya
>
> In general, what kind of improvements actually needed for live migration?
>
> Thanks,
> Takuya
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-30 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111114182041.43570cdf.yoshikawa.takuya@oss.ntt.co.jp>
[not found] ` <4EC0EC90.1090202@redhat.com>
[not found] ` <4EC0F3D3.9090907@oss.ntt.co.jp>
[not found] ` <4EC10BFE.7050704@redhat.com>
2011-11-16 8:17 ` [Qemu-devel] [PATCH 0/4] KVM: Dirty logging optimization using rmap Takuya Yoshikawa
[not found] ` <4EC33C0B.1060807@oss.ntt.co.jp>
[not found] ` <4EC37D18.4010609@redhat.com>
[not found] ` <loom.20111129T104524-678@post.gmane.org>
[not found] ` <4ED4AF43.2040003@linux.vnet.ibm.com>
[not found] ` <4ED4B574.8090907@oss.ntt.co.jp>
[not found] ` <4ED4BFEB.5010600@redhat.com>
[not found] ` <4ED4C85A.5020509@linux.vnet.ibm.com>
[not found] ` <4ED4C9A3.50504@redhat.com>
[not found] ` <4ED4E626.5010507@redhat.com>
2011-11-30 5:02 ` Takuya Yoshikawa
2011-11-30 5:15 ` Takuya Yoshikawa [this message]
2011-12-01 15:18 ` Avi Kivity
2011-12-03 4:37 ` Takuya Yoshikawa
2011-12-04 10:20 ` Avi Kivity
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=4ED5BC03.5000901@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=xiaoguangrong@linux.vnet.ibm.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).