[v1] migration: Tally pre-copy, downtime and post-copy bytes independently

[RFC 0/2] migration: Tally pre-copy, downtime and post-copy bytes independently

David Edmondson posted 2 patches 2 years, 4 months ago

Diff against v2 v3
Download series mbox

Test checkpatch passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20211216123420.1328937-1-david.edmondson@oracle.com

Maintainers: Markus Armbruster <armbru@redhat.com>, Juan Quintela <quintela@redhat.com>, Eric Blake <eblake@redhat.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>

There is a newer version of this series

migration/migration.c |  3 +++
migration/ram.c       | 30 +++++++++++++++++++++---------
migration/ram.h       |  1 +
monitor/hmp-cmds.c    | 12 ++++++++++++
qapi/migration.json   |  4 +++-
5 files changed, 40 insertions(+), 10 deletions(-)

Expand all Fold all

[RFC 0/2] migration: Tally pre-copy, downtime and post-copy bytes independently

Posted by David Edmondson 2 years, 4 months ago

When examining a report of poor migration behaviour, it would often be
useful to understand how much data was transferred in different phases
of the migration process.

For example, if the downtime limit is exceeded, to know how much data
was transferred during the downtime.

RFC because the name "ram_transferred_add" doesn't seem great, and I'm
unsure whether the tests to determine the phase in the second patch
are the most appropriate.

David Edmondson (2):
  migration: Introduce ram_transferred_add()
  migration: Tally pre-copy, downtime and post-copy bytes independently

 migration/migration.c |  3 +++
 migration/ram.c       | 30 +++++++++++++++++++++---------
 migration/ram.h       |  1 +
 monitor/hmp-cmds.c    | 12 ++++++++++++
 qapi/migration.json   |  4 +++-
 5 files changed, 40 insertions(+), 10 deletions(-)

-- 
2.33.0