From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>
Cc: amit.shah@redhat.com, thomas.knauth@googlemail.com,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC 3/3] migration: use checkpoint during migration
Date: Tue, 17 Nov 2015 16:05:32 +0000 [thread overview]
Message-ID: <20151117160531.GM2498@work-vm> (raw)
In-Reply-To: <564B49E1.4060002@mailbox.tu-dresden.de>
* Bohdan Trach (bohdan.trach@mailbox.tu-dresden.de) wrote:
>
> On 11/17/2015 01:26 PM, Dr. David Alan Gilbert wrote:
> > There are a couple of things I don't understand about this:
> > 1) How does the source fill it's hashes table? Is it just given the same
> > dump file as the destination?
> > 2) Why does RAM_SAVE_FLAG_PAGE_HASH exist; if you're sending the full page
> > to the destination, why do we also send the hash?
>
> 1. Migration source is assumed to have the same dump file as the
> destination. The design was optimized for the case of ping-pong
> migrations over SAN, where checkpoint file is always available. We
> also have proof-of-concept code that transfers available hashes from
> the migration destination to the source over the network, but it
> didn't make it into these patches.
OK, it's easy with the SAN then.
> 2. We send the hash to avoid hash calculations on the receiving side
> to save some CPU time. This flag can be removed, as I don't think the
> benefits it provides are big.
Why is the hash needed on the destination; if it's a page which the source
has decided isn't in a matching page, what does the destination use the
hash for?
> > I think there's a problem here that given the source is still running it's CPU and changing
> > memory; it can be writing to the page at the same time, so the page you send might not
> > match the hash you send; we're guaranteed to resend the page again if it was written
> > to, but that still doesn't make these two things match; although as I say above
> > I'm not sure why SAVE_FLAG_PAGE_HASH exists.
>
> This is true. In this case, we will just delete the SAVE_FLAG_PAGE_HASH flag.
But how do you know to delete the SAVE_FLAG_PAGE_HASH flag?
Dave
>
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
> --
> With best regards,
> Bohdan Trach
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-11-17 16:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 12:12 [Qemu-devel] [PATCH RFC 0/3] Checkpoint-assisted migration proposal Bohdan Trach
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 1/3] memory: Add dump-pc-mem command for checkpointing Bohdan Trach
2015-04-17 13:53 ` Eric Blake
2015-04-18 7:40 ` Bohdan Trach
2015-11-16 16:46 ` Dr. David Alan Gilbert
2015-11-17 15:38 ` Bohdan Trach
2015-11-17 16:02 ` Dr. David Alan Gilbert
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 2/3] memory: implement checkpoint handling Bohdan Trach
2015-11-16 16:56 ` Dr. David Alan Gilbert
2015-11-17 15:38 ` Bohdan Trach
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 3/3] migration: use checkpoint during migration Bohdan Trach
2015-11-17 12:26 ` Dr. David Alan Gilbert
2015-11-17 15:38 ` Bohdan Trach
2015-11-17 16:05 ` Dr. David Alan Gilbert [this message]
2015-11-17 16:34 ` Bohdan Trach
2015-11-17 16:39 ` Dr. David Alan Gilbert
2015-04-24 11:38 ` [Qemu-devel] [PATCH RFC, Ping 0/3] Checkpoint-assisted migration proposal Bohdan Trach
2015-05-11 11:13 ` Amit Shah
2015-06-09 10:00 ` Bohdan Trach
2015-08-19 9:19 ` Bohdan Trach
2015-09-15 10:39 ` [Qemu-devel] [PATCH RFC " Amit Shah
2015-10-05 8:33 ` Thomas Knauth
2015-10-05 8:59 ` Amit Shah
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=20151117160531.GM2498@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=bohdan.trach@mailbox.tu-dresden.de \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thomas.knauth@googlemail.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.