From: Juan Quintela <quintela@redhat.com>
To: Hyman Huang <yong.huang@smartx.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Leonardo Bras <leobras@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [v3 6/6] docs/migration: Add the dirty limit section
Date: Thu, 02 Nov 2023 11:37:05 +0100 [thread overview]
Message-ID: <87lebg30ha.fsf@secure.mitica> (raw)
In-Reply-To: <0f2b2c63fec22ea23e4926cdeb567b7a0ebd8152.1698847223.git.yong.huang@smartx.com> (Hyman Huang's message of "Wed, 1 Nov 2023 22:04:09 +0800")
Hyman Huang <yong.huang@smartx.com> wrote:
> The dirty limit feature has been introduced since the 8.1
> QEMU release but has not reflected in the document, add a
> section for that.
>
> Signed-off-by: Hyman Huang <yong.huang@smartx.com>
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
> Message-Id: <36194a8a23d937392bf13d9fff8e898030c827a3.1697815117.git.yong.huang@smartx.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
I queued the whole series. I didn't comment about the guestperf script
changes because I am not familiar with that part.
> ---
> docs/devel/migration.rst | 71 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 71 insertions(+)
>
> diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
> index be913630c3..12c35f9bc4 100644
> --- a/docs/devel/migration.rst
> +++ b/docs/devel/migration.rst
> @@ -590,6 +590,77 @@ path.
> Return path - opened by main thread, written by main thread AND postcopy
> thread (protected by rp_mutex)
>
> +Dirty limit
> +=====================
Too long, I fixed it by hand.
prev parent reply other threads:[~2023-11-02 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:04 [v3 0/6] dirtylimit: miscellaneous patches Hyman Huang
2023-11-01 14:04 ` [v3 1/6] system/dirtylimit: Fix a race situation Hyman Huang
2023-11-02 10:28 ` Juan Quintela
2023-11-01 14:04 ` [v3 2/6] system/dirtylimit: Drop the reduplicative check Hyman Huang
2023-11-02 10:28 ` Juan Quintela
2023-11-01 14:04 ` [v3 3/6] tests: Add migration dirty-limit capability test Hyman Huang
2023-11-02 10:31 ` Juan Quintela
2023-11-01 14:04 ` [v3 4/6] tests/migration: Introduce dirty-ring-size option into guestperf Hyman Huang
2023-11-01 14:04 ` [v3 5/6] tests/migration: Introduce dirty-limit " Hyman Huang
2023-11-01 14:04 ` [v3 6/6] docs/migration: Add the dirty limit section Hyman Huang
2023-11-02 10:37 ` Juan Quintela [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=87lebg30ha.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yong.huang@smartx.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 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.