qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: huangy81@chinatelecom.cn
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Hyman Huang(黄勇)" <huangy81@chinatelecom.cn>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>
Subject: [PATCH v1] introduce multifd into guestperf
Date: Sat, 20 Mar 2021 01:04:27 +0800	[thread overview]
Message-ID: <cover.1616171924.git.huangy81@chinatelecom.cn> (raw)

From: Hyman Huang(黄勇) <huangy81@chinatelecom.cn>

This is the v1 of guestperf multifd migration support

It is merely the same as the original patch, just change the maintainer,
since the ./scripts/get_maintainer.pl do not get the maintainer of 
tests/migration before this patch:
https://lore.kernel.org/qemu-devel/842e7cbd-a444-04ac-35d5-168c6415441e@redhat.com/

Guestperf tool does not cover the multifd-enabled migration currently, it
is worth supporting so that developers can analysis the migration performance
with all kinds of migration. 

Please review, thanks.

Hyman (1):
  tests/migration: introduce multifd into guestperf

 tests/migration/guestperf/comparison.py | 14 ++++++++++++++
 tests/migration/guestperf/engine.py     | 16 ++++++++++++++++
 tests/migration/guestperf/scenario.py   | 12 ++++++++++--
 tests/migration/guestperf/shell.py      | 10 +++++++++-
 4 files changed, 49 insertions(+), 3 deletions(-)

-- 
1.8.3.1



             reply	other threads:[~2021-03-19 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 17:04 huangy81 [this message]
2021-03-19 17:04 ` [PATCH v1] tests/migration: introduce multifd into guestperf huangy81
2021-03-24  1:18   ` Hyman Huang
2021-04-21  1:48     ` Hyman Huang
2021-04-30  8:33   ` Daniel P. Berrangé
2021-05-11  9:54     ` Dr. David Alan Gilbert

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=cover.1616171924.git.huangy81@chinatelecom.cn \
    --to=huangy81@chinatelecom.cn \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).