From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: [PATCH v3 00/12] Migration: Make more ram_counters atomic
Date: Wed, 19 Apr 2023 18:24:03 +0200 [thread overview]
Message-ID: <20230419162415.16260-1-quintela@redhat.com> (raw)
Hi
In this 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 (12):
migration: Merge ram_counters and ram_atomic_counters
migration: Update atomic stats out of the mutex
migration: Make multifd_bytes atomic
migration: Make dirty_sync_missed_zero_copy atomic
migration: Make precopy_bytes atomic
migration: Make downtime_bytes atomic
migration: Make dirty_sync_count atomic
migration: Make postcopy_requests atomic
migration: Make dirty_pages_rate atomic
migration: Make dirty_bytes_last_sync atomic
migration: Rename duplicate to zero_pages
migration: Rename normal to full_pages
migration/ram.h | 34 ++++++++++-----------
migration/migration.c | 34 ++++++++++++---------
migration/multifd.c | 10 +++---
migration/ram.c | 71 +++++++++++++++++++------------------------
4 files changed, 73 insertions(+), 76 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-19 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 16:24 Juan Quintela [this message]
2023-04-19 16:24 ` [PATCH v3 01/12] migration: Merge ram_counters and ram_atomic_counters Juan Quintela
2023-04-19 16:24 ` [PATCH v3 02/12] migration: Update atomic stats out of the mutex Juan Quintela
2023-04-19 16:24 ` [PATCH v3 03/12] migration: Make multifd_bytes atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 04/12] migration: Make dirty_sync_missed_zero_copy atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 05/12] migration: Make precopy_bytes atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 06/12] migration: Make downtime_bytes atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 07/12] migration: Make dirty_sync_count atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 08/12] migration: Make postcopy_requests atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 09/12] migration: Make dirty_pages_rate atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 10/12] migration: Make dirty_bytes_last_sync atomic Juan Quintela
2023-04-19 16:24 ` [PATCH v3 11/12] migration: Rename duplicate to zero_pages Juan Quintela
2023-04-19 16:24 ` [PATCH v3 12/12] migration: Rename normal to full_pages Juan Quintela
2023-04-19 19:29 ` [PATCH v3 00/12] Migration: Make more ram_counters atomic Peter Xu
2023-04-19 19:54 ` Juan Quintela
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=20230419162415.16260-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).