From: Juan Quintela <quintela@redhat.com>
To: Lukas Straub <lukasstraub2@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, Peter Xu <peterx@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 01/13] qtest/migration-test.c: Add postcopy tests with compress enabled
Date: Thu, 20 Apr 2023 23:12:02 +0200 [thread overview]
Message-ID: <875y9quul9.fsf@secure.mitica> (raw)
In-Reply-To: <20230420103756.2aada33a@gecko.fritz.box> (Lukas Straub's message of "Thu, 20 Apr 2023 12:37:56 +0200")
Lukas Straub <lukasstraub2@web.de> wrote:
> On Thu, 20 Apr 2023 12:20:25 +0200
> Juan Quintela <quintela@redhat.com> wrote:
>
>> Lukas Straub <lukasstraub2@web.de> wrote:
>> > Add postcopy tests with compress enabled to ensure nothing breaks
>> > with the refactoring in the next commits.
>> >
>> > preempt+compress is blocked, so no test needed for that case.
>> >
>> > Signed-off-by: Lukas Straub <lukasstraub2@web.de>
>>
>> Reviewed-by: Juan Quintela <quintela@redhat.com>
>>
>> And I wanted to removed the old compression code and it gets new users. Sniff.
>
> Who know how many compress threads users are out there...
Not too much.
We broke it during development and nobody found it.
And the reason that I wrote the multifd-zlib compression code was
because I was not able to get a migration-test working with compression,
so ....
> By the way, I'm not against deprecating compress threads in the long
> run. I'm already working on (cleanly :)) adding colo support with
> multifd.
Ok, then I will still put the deprecate comment there.
>> > ---
>> > tests/qtest/migration-test.c | 83 +++++++++++++++++++++++-------------
>> > 1 file changed, 53 insertions(+), 30 deletions(-)
>> >
>> > diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
>> > index 1f2a019ce0..930cb4f29d 100644
>> > --- a/tests/qtest/migration-test.c
>> > +++ b/tests/qtest/migration-test.c
>> > @@ -1127,6 +1127,36 @@ test_migrate_tls_x509_finish(QTestState *from,
>> > #endif /* CONFIG_TASN1 */
>> > #endif /* CONFIG_GNUTLS */
>> >
>> > +static void *
>> > +test_migrate_compress_start(QTestState *from,
>> > + QTestState *to)
>> > +{
>> > + migrate_set_parameter_int(from, "compress-level", 1);
>> > + migrate_set_parameter_int(from, "compress-threads", 4);
>> > + migrate_set_parameter_bool(from, "compress-wait-thread", true);
>> > + migrate_set_parameter_int(to, "decompress-threads", 4);
>> > +
>> > + migrate_set_capability(from, "compress", true);
>> > + migrate_set_capability(to, "compress", true);
>> > +
>> > + return NULL;
>> > +}
>>
>> Independently of this patch, we need to change this test to use 4
>> compression tests and 3 decompression or anything that is not the same
>> number in both sides.
>>
>> I was complaining about this and when I arrived to the end of the path
>> found that this was code movement.
>>
>> Later, Juan.
>>
>
> Oops, forgot to mention, the test is based on this patch
> https://lore.kernel.org/qemu-devel/2f4abb67cf5f3e1591b2666676462a93bdd20bbc.1680618040.git.lukasstraub2@web.de/
>
> Will probably carry the patch with this series then. So you mean 4
> compress _threads_ and 3 decompress _threads_?
Yeap.
Later, Juan.
next prev parent reply other threads:[~2023-04-20 21:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 9:47 [PATCH v2 00/13] migration/ram.c: Refactor compress code Lukas Straub
2023-04-20 9:47 ` [PATCH v2 01/13] qtest/migration-test.c: Add postcopy tests with compress enabled Lukas Straub
2023-04-20 10:20 ` Juan Quintela
2023-04-20 10:37 ` Lukas Straub
2023-04-20 21:12 ` Juan Quintela [this message]
2023-04-20 9:47 ` [PATCH v2 02/13] ram.c: Let the compress threads return a CompressResult enum Lukas Straub
2023-04-20 21:13 ` Juan Quintela
2023-04-20 9:47 ` [PATCH v2 03/13] ram.c: Dont change param->block in the compress thread Lukas Straub
2023-04-20 21:13 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 04/13] ram.c: Reset result after sending queued data Lukas Straub
2023-04-28 11:59 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 05/13] ram.c: Do not call save_page_header() from compress threads Lukas Straub
2023-04-28 12:02 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 06/13] ram.c: Call update_compress_thread_counts from compress_send_queued_data Lukas Straub
2023-04-28 12:10 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 07/13] ram.c: Remove last ram.c dependency from the core compress code Lukas Straub
2023-04-28 12:14 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 08/13] ram.c: Introduce whitespace (squash with next patch) Lukas Straub
2023-04-28 16:13 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 09/13] ram.c: Move core compression code into its own file Lukas Straub
2023-04-20 9:48 ` [PATCH v2 10/13] ram.c: Remove whitespace (squash with previous patch) Lukas Straub
2023-04-28 16:15 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 11/13] ram.c: Move core decompression code into its own file Lukas Straub
2023-04-28 17:22 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 12/13] ram compress: Assert that the file buffer matches the result Lukas Straub
2023-04-28 17:24 ` Juan Quintela
2023-04-20 9:48 ` [PATCH v2 13/13] ram-compress.c: Make target independent Lukas Straub
2023-04-28 17:29 ` Juan Quintela
2023-04-20 9:59 ` [PATCH v2 14/13] migration: Initialize and cleanup decompression in migration.c Lukas Straub
2023-04-28 17:33 ` 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=875y9quul9.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=lukasstraub2@web.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).