From: Eric Blake <eblake@redhat.com>
To: Zeyu Jin <jinzeyu@huawei.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: Mon, 30 Nov 2020 10:42:57 -0600 [thread overview]
Message-ID: <2ec8cee7-5330-0e87-f593-464ba789688e@redhat.com> (raw)
In-Reply-To: <20201127093639.2815-1-jinzeyu@huawei.com>
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.
> 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'
> 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%.
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-11-30 16:45 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 [this message]
2020-12-01 6:04 ` Zeyu Jin
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=2ec8cee7-5330-0e87-f593-464ba789688e@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jinzeyu@huawei.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).