From: Hyman Huang <yong.huang@smartx.com>
To: qemu-devel@nongnu.org
Cc: Hyman Huang <yong.huang@smartx.com>
Subject: [PULL 0/2] Dirty page rate and dirty page limit 20231010 patches
Date: Tue, 10 Oct 2023 08:31:52 +0800 [thread overview]
Message-ID: <cover.1696896603.git.yong.huang@smartx.com> (raw)
The following changes since commit 2f3913f4b2ad74baeb5a6f1d36efbd9ecdf1057d:
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2023-10-05 09:01:01 -0400)
are available in the Git repository at:
https://github.com/newfriday/qemu.git tags/dirtylimit-dirtyrate-pull-request-20231010
for you to fetch changes up to 320a6ccc769dc09ae7ad0b4838e322018f334bf4:
migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time (2023-10-10 08:04:12 +0800)
----------------------------------------------------------------
Dirtylimit and dirtyrate 20231010 patches PULL request
Dirty page rate measurement optimization.
Please apply, thanks, Yong.
----------------------------------------------------------------
Andrei Gudkov (2):
migration/calc-dirty-rate: millisecond-granularity period
migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time
migration/dirtyrate.c | 122 +++++++++++++++++++++++++++---------------
migration/dirtyrate.h | 12 +++--
qapi/migration.json | 58 ++++++++++++++++----
3 files changed, 134 insertions(+), 58 deletions(-)
--
2.39.1
next reply other threads:[~2023-10-10 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 0:31 Hyman Huang [this message]
2023-10-10 0:31 ` [PULL 1/2] migration/calc-dirty-rate: millisecond-granularity period Hyman Huang
2023-10-10 0:31 ` [PULL 2/2] migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time Hyman Huang
2023-10-10 16:32 ` [PULL 0/2] Dirty page rate and dirty page limit 20231010 patches Stefan Hajnoczi
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.1696896603.git.yong.huang@smartx.com \
--to=yong.huang@smartx.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).