qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <lieven-lists@dlhnet.de>
Cc: aik@ozlabs.ru, pbonzini@redhat.com, Peter Lieven <pl@kamp.de>,
	qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] Revert "migration: do not sent zero pages	in bulk stage"
Date: Sat, 15 Jun 2013 16:28:13 +0100	[thread overview]
Message-ID: <51BC880D.8010106@redhat.com> (raw)
In-Reply-To: <51B09C19.8090002@dlhnet.de>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

On 06/06/2013 03:26 PM, Peter Lieven wrote:

>>> @@ -514,8 +512,8 @@
>>>   ##
>>>   { 'type': 'MigrationStats',
>>>     'data': {'transferred': 'int', 'remaining': 'int', 'total': 'int' ,
>>> -           'duplicate': 'int', 'skipped': 'int', 'normal': 'int',
>>> -           'normal-bytes': 'int', 'dirty-pages-rate' : 'int' } }
>>> +           'duplicate': 'int', 'normal': 'int', 'normal-bytes': 'int',
>>> +           'dirty-pages-rate' : 'int' } }
>> This hunk is questionable.  Removing something that we have previously
>> sent
>> over the wire may break clients that are expecting this field to exist.
>> Rather than reverting the entire patch, you should consider keeping this
>> field present in QMP, even if you now always populate it with 0.
>>
> You are right. I might still account zero pages in the bulk phase to
> give this
> field a meaning. These pages are very likely not written on the
> destination except
> for the cornercases. What do you think?

I don't care if you document a slightly different meaning for the
statistic; as long as it is documented.  Where I do care is removing
something that previous versions provided; I think your later versions
of this series adequately took care of this by reverting only a subset
of the original patch.  I'm okay with the current qemu.git behavior that
always displays returns "skipped":0, or if you post a later patch that
again makes it print a non-zero number that you find useful.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-06-15 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  8:36 [Qemu-devel] [PATCH 0/2] fix migration of zero pages Peter Lieven
2013-06-06  8:36 ` [Qemu-devel] [PATCH 1/2] Revert "migration: do not sent zero pages in bulk stage" Peter Lieven
2013-06-06 12:16   ` Eric Blake
2013-06-06 14:26     ` Peter Lieven
2013-06-15 15:28       ` Eric Blake [this message]
2013-06-19 10:10   ` Paolo Bonzini
2013-06-06  8:36 ` [Qemu-devel] [PATCH 2/2] migration: do not overwrite zero pages Peter Lieven
2013-06-19 10:10   ` Paolo Bonzini
2013-06-24 14:59     ` Alexey Kardashevskiy

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=51BC880D.8010106@redhat.com \
    --to=eblake@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=lieven-lists@dlhnet.de \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).