From: Zeyu Jin <jinzeyu@huawei.com>
To: Eric Blake <eblake@redhat.com>, <quintela@redhat.com>,
<dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, zhang.zhanghailiang@huawei.com
Subject: Re: [PATCH v2 0/6] migration: Multi-thread compression method support
Date: Tue, 1 Dec 2020 14:04:06 +0800 [thread overview]
Message-ID: <df92d5da-d38c-3b73-488e-2e69c48d2a13@huawei.com> (raw)
In-Reply-To: <2ec8cee7-5330-0e87-f593-464ba789688e@redhat.com>
On 2020/12/1 0:42, Eric Blake wrote:
> On 11/27/20 3:36 AM, Zeyu Jin wrote:
>
> Meta-comment: you appear to be having problems threading your series;
> I've now seen three separate cover letters (RFC v1, v2 with no subject,
> v2 with subject) and two series where each patch was a separate thread.
> It is difficult to follow which messages are related when reading in a
> mail client that sorts by most-recently-active thread first. You may
> want to investigate why your threading is not working, although I'd wait
> to send v3 until you have actual changes to incorporate.
>
Thank you for noticing that. It`s my mistake when sending patches.
Everything will be fine in v3.
>> Currently we have both multi-thread compression and multifd to optimize
>> live migration in Qemu. Mulit-thread compression deals with the situation
>> where network bandwith is limited but cpu resource adequate. Multifd instead
>
> Not that typos in the cover letter matter, but this should be 'bandwidth'
>
Yes, I will fix that.
>> aims to take full advantage of network bandwith. Moreover it supports both
>> zlib and zstd compression on each channel.
>>
>> In this patch series, we did some code refactoring on multi-thread compression
>> live migration and bring zstd compression method support for it.
>>
>> Below is the test result of multi-thread compression live migration
>> with different compress methods. Test result shows that zstd outperforms
>> zlib by about 70%.
>>
>
prev parent reply other threads:[~2020-12-01 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 9:36 [PATCH v2 0/6] migration: Multi-thread compression method support Zeyu Jin
2020-11-30 16:42 ` Eric Blake
2020-12-01 6:04 ` Zeyu Jin [this message]
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=df92d5da-d38c-3b73-488e-2e69c48d2a13@huawei.com \
--to=jinzeyu@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhang.zhanghailiang@huawei.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).