From: Peter Xu <peterx@redhat.com>
To: Hyman <huangy81@chinatelecom.cn>
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
"David Hildenbrand" <david@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v22 0/8] support dirty restraint on vCPU
Date: Sun, 24 Apr 2022 17:55:18 -0400 [thread overview]
Message-ID: <YmXHRrZZA21Sxfv7@xz-m1.local> (raw)
In-Reply-To: <fb74d6af-49e7-ffd9-6bb0-66acb7407c8c@chinatelecom.cn>
Hi, Yong,
On Mon, Apr 25, 2022 at 12:52:45AM +0800, Hyman wrote:
> Ping.
> Hi, David and Peter, how do you think this patchset?
> Is it suitable for queueing ? or is there still something need to be done ?
It keeps looking good to me in general, let's see whether the maintainers
have any comments. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-04-24 21:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 17:49 [PATCH v22 0/8] support dirty restraint on vCPU huangy81
2022-03-31 17:49 ` [PATCH v22 1/8] accel/kvm/kvm-all: Refactor per-vcpu dirty ring reaping huangy81
2022-03-31 17:49 ` [PATCH v22 2/8] cpus: Introduce cpu_list_generation_id huangy81
2022-03-31 17:49 ` [PATCH v22 3/8] migration/dirtyrate: Refactor dirty page rate calculation huangy81
2022-03-31 17:49 ` [PATCH v22 4/8] softmmu/dirtylimit: Implement vCPU dirtyrate calculation periodically huangy81
2022-03-31 17:49 ` [PATCH v22 5/8] accel/kvm/kvm-all: Introduce kvm_dirty_ring_size function huangy81
2022-03-31 17:49 ` [PATCH v22 6/8] softmmu/dirtylimit: Implement virtual CPU throttle huangy81
2022-03-31 17:49 ` [PATCH v22 7/8] softmmu/dirtylimit: Implement dirty page rate limit huangy81
2022-03-31 17:49 ` [PATCH v22 8/8] tests: Add dirty page rate limit test huangy81
2022-03-31 18:33 ` Peter Xu
2022-04-24 16:52 ` [PATCH v22 0/8] support dirty restraint on vCPU Hyman
2022-04-24 21:55 ` Peter Xu [this message]
2022-04-27 6:21 ` Markus Armbruster
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=YmXHRrZZA21Sxfv7@xz-m1.local \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eduardo@habkost.net \
--cc=huangy81@chinatelecom.cn \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.