From: Juan Quintela <quintela@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: Re: [PATCH v2 2/6] ram: Let colo_flush_ram_cache take the bitmap_mutex
Date: Tue, 09 May 2023 12:44:58 +0200 [thread overview]
Message-ID: <87ttwleqc5.fsf@secure.mitica> (raw)
In-Reply-To: <35cb23ba854151d38a31e3a5c8a1020e4283cb4a.1683572883.git.lukasstraub2@web.de> (Lukas Straub's message of "Mon, 8 May 2023 21:10:55 +0200")
Lukas Straub <lukasstraub2@web.de> wrote:
> This is not required, colo_flush_ram_cache does not run concurrently
> with the multifd threads since the cache is only flushed after
> everything has been received. But it makes me more comfortable.
>
> This will be used in the next commits to add colo support to multifd.
>
> Signed-off-by: Lukas Straub <lukasstraub2@web.de>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2023-05-09 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 19:10 [PATCH v2 0/6] multifd: Add colo support Lukas Straub
2023-05-08 19:10 ` [PATCH v2 1/6] ram: Add public helper to set colo bitmap Lukas Straub
2023-05-09 10:44 ` Juan Quintela
2023-05-08 19:10 ` [PATCH v2 2/6] ram: Let colo_flush_ram_cache take the bitmap_mutex Lukas Straub
2023-05-09 10:44 ` Juan Quintela [this message]
2023-05-08 19:11 ` [PATCH v2 3/6] multifd: Introduce multifd-internal.h Lukas Straub
2023-05-08 19:11 ` [PATCH v2 4/6] multifd: Introduce a overridable revc_pages method Lukas Straub
2023-05-08 19:11 ` [PATCH v2 5/6] multifd: Add the ramblock to MultiFDRecvParams Lukas Straub
2023-05-09 10:45 ` Juan Quintela
2023-05-08 19:11 ` [PATCH v2 6/6] multifd: Add colo support Lukas Straub
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=87ttwleqc5.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=leobras@redhat.com \
--cc=lukasstraub2@web.de \
--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).