Migration: Make more ram_counters atomic
v4 cover Migration: Make more ram_counters atomic
Hi
In this v4:
- Change aligned_uint64_t to size_t to make (some) 32bit hosts happy.
Please review.
[v3]
- Addressed reviews
- All counters are now atomic, either Stat64 or atomic.
- Rename duplicated to zero_pages
- Rename normal to zero_pages.
Please review.
[v2]
- fix typos found by David Edmondson
- Add review-by tags.
Please review.
[v1]
On previous series we cerate ram_atomic_counters. But we basically need that all counters are atomic. So move back to only have ram_counters, just with a new type that allows the atomic counters.
Once there, move update of stats out of RAM mutex. And make multifd_bytes atomic.
Later, Juan.
Juan Quintela (2):
migration: Make dirty_pages_rate atomic
migration: Make dirty_bytes_last_sync atomic
migration/migration.c | 10 +++++++--- migration/ram.c | 8 +++++--- migration/ram.h | 4 ++-- 3 files changed, 14 insertions(+), 8 deletions(-)
Signature · 1 line
2.39.2
PATCH v4 1/2 migration: Make dirty_pages_rate atomic
In this case we use qatomic operations instead of Stat64 wrapper because there is no stat64_set(). Defining the 64 bit wrapper is trivial. The one without atomics is more interesting.
---
Change aligned_uint64_t to size_t to make (some) 32bit hosts happy.
--- migration/migration.c | 6 ++++-- migration/ram.c | 5 +++-- migration/ram.h | 2 +- 3 files changed, 8 insertions(+), 5 deletions(-)
migration/migration.c +4 -2
@@ -1014,7 +1014,8 @@ static void populate_ram_info(MigrationInfo *info, MigrationState *s)if (s->state !=MIGRATION_STATUS_COMPLETED ) { info->ram->remaining =ram_bytes_remaining (); - info->ram->dirty_pages_rate = ram_counters.dirty_pages_rate; + info->ram->dirty_pages_rate = +qatomic_read__nocheck (&ram_counters.dirty_pages_rate); } }
@@ -3180,7 +3181,8 @@ static void migration_update_counters(MigrationState *s,* if we haven't sent anything, we don't want to * recalculate. 10000 is a small enough number for our purposes */ -if (ram_counters.dirty_pages_rate && transferred >10000 ) { +if (qatomic_read__nocheck (&ram_counters.dirty_pages_rate) && + transferred >10000 ) { s->expected_downtime = ram_counters.remaining / bandwidth; }
migration/ram.c +3 -2
@@ -1129,8 +1129,9 @@ static void migration_update_rates(RAMState *rs, int64_t end_time)double compressed_size;/* calculate period counters */ - ram_counters.dirty_pages_rate = rs->num_dirty_pages_period *1000 - / (end_time - rs->time_last_bitmap_sync); +qatomic_set__nocheck (&ram_counters.dirty_pages_rate, + rs->num_dirty_pages_period *1000 / + (end_time - rs->time_last_bitmap_sync));if (!page_count) {return ;
migration/ram.h +1 -1
@@ -41,7 +41,7 @@* one thread). */ typedef struct { - int64_t dirty_pages_rate; + size_t dirty_pages_rate; Stat64 dirty_sync_count; Stat64 dirty_sync_missed_zero_copy; Stat64 downtime_bytes;
Signature · 1 line
2.39.2
PATCH v4 2/2 migration: Make dirty_bytes_last_sync atomic
In reply to Juan QuintelaAs we set its value, it needs to be operated with atomics. We rename it from remaining to better reflect its meaning.
Statistics always return the real reamaining bytes. This was used to store how much pages where dirty on the previous generation, so we can calculate the expected downtime as: dirty_bytes_last_sync / current_bandwith.
If we use the actual remaining bytes, we would see a very small value at the end of the iteration.
---
I am open to use ram_bytes_remaining() in its only use and be more "optimistic" about the downtime.
Change aligned_uint64_t to size_t to make (some) 32bit hosts happy.
--- migration/migration.c | 4 +++- migration/ram.c | 3 ++- migration/ram.h | 2 +- 3 files changed, 6 insertions(+), 3 deletions(-)
migration/migration.c +3 -1
@@ -3183,7 +3183,9 @@ static void migration_update_counters(MigrationState *s,*/ if (qatomic_read__nocheck (&ram_counters.dirty_pages_rate) && transferred >10000 ) { - s->expected_downtime = ram_counters.remaining / bandwidth; + s->expected_downtime = +qatomic_read__nocheck (&ram_counters.dirty_bytes_last_sync) / + bandwidth; }qemu_file_reset_rate_limit (s->to_dst_file);
migration/ram.c +2 -1
@@ -1223,7 +1223,8 @@ static void migration_bitmap_sync(RAMState *rs)RAMBLOCK_FOREACH_NOT_IGNORED (block) {ramblock_sync_dirty_bitmap (rs, block); } - ram_counters.remaining =ram_bytes_remaining (); +qatomic_set__nocheck (&ram_counters.dirty_bytes_last_sync, +ram_bytes_remaining ()); }qemu_mutex_unlock (&rs->bitmap_mutex);
migration/ram.h +1 -1
@@ -41,6 +41,7 @@* one thread). */ typedef struct { + size_t dirty_bytes_last_sync; size_t dirty_pages_rate; Stat64 dirty_sync_count; Stat64 dirty_sync_missed_zero_copy;
@@ -51,7 +52,6 @@ typedef struct {Stat64 postcopy_bytes;Stat64 postcopy_requests;Stat64 precopy_bytes; -int64_t remaining;Stat64 transferred; } RAMStats;
Signature · 1 line
2.39.2
Quoted 6 lines · Juan Quintela
Hi
In this v4:
- Changealigned_uint64_ttosize_tto make (some) 32bit hosts happy.Please review.
self-NACK
Still missing the removal of the __nocheck() functions.
Quoted 33 lines
[v3]
- Addressed reviews
- All counters are now atomic, either Stat64 or atomic.
- Rename duplicated tozero_pages
- Rename normal tozero_pages.Please review.
[v2]
- fix typos found by David Edmondson
- Add review-by tags.Please review.
[v1]
On previous series we cerateram_atomic_counters. But we basically need that all counters are atomic. So move back to only haveram_counters, just with a new type that allows the atomic counters.Once there, move update of stats out of RAM mutex. And make
multifd_bytesatomic.Later, Juan.
Juan Quintela (2):
migration: Makedirty_pages_rateatomic
migration: Makedirty_bytes_last_syncatomicmigration/migration.c | 10 +++++++--- migration/ram.c | 8 +++++--- migration/ram.h | 4 ++-- 3 files changed, 14 insertions(+), 8 deletions(-)