From: Paolo Bonzini <pbonzini@redhat.com>
To: "Li, Liang Z" <liang.z.li@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
'Kevin Wolf' <kwolf@redhat.com>,
'Juan Quintela' <quintela@redhat.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Subject: Re: [Qemu-devel] FW: about the bdrv_invalidate_cache_all()
Date: Wed, 5 Aug 2015 19:45:14 +0200 [thread overview]
Message-ID: <55C24BAA.5090704@redhat.com> (raw)
In-Reply-To: <F2CBF3009FA73547804AE4C663CAB28E589F3E@shsmsx102.ccr.corp.intel.com>
On 05/08/2015 17:21, Li, Liang Z wrote:
> I found the function bdrv_invalidate_cache_all() in the
> process_incoming_migration_co() takes more the 10ms when doing live
> migration with shared storage, which prolong the service down time.
>
> The bdrv_invalidate_cache_all() is needed when doing the live
> migration with '-b' option. For live migration with share storage,
> such as nfs, is it still needed? If so, could please tell me why? If
> not, I think we can do some optimization.
IIUC it's the other way round. bdrv_invalidate_cache_all() is only
needed for live migration with shared storage.
Paolo
prev parent reply other threads:[~2015-08-05 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 15:21 [Qemu-devel] FW: about the bdrv_invalidate_cache_all() Li, Liang Z
2015-08-05 17:45 ` Paolo Bonzini [this message]
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=55C24BAA.5090704@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=liang.z.li@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yang.z.zhang@intel.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.