From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
qemu-arm@nongnu.org, wanghaibin.wang@huawei.com,
Keqian Zhu <zhukeqian1@huawei.com>
Subject: Re: [PATCH] migration/throttle: Add throttle-trig-thres migration parameter
Date: Thu, 12 Mar 2020 17:02:19 +0000 [thread overview]
Message-ID: <20200312170219.GK3211@work-vm> (raw)
In-Reply-To: <2db47b97-729f-4ccb-dab2-585771acc2fe@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 2/20/20 8:57 PM, Keqian Zhu wrote:
> > Currently, if the bytes_dirty_period is more than the 50% of
> > bytes_xfer_period, we start or increase throttling.
> >
> > If we make this percentage higher, then we can tolerate higher
> > dirty rate during migration, which means less impact on guest.
> > The side effect of higher percentage is longer migration time.
> >
> > We can configure this parameter to switch between migration time
> > firt or guest performance first. The default value is 50.
> >
> > Signed-off-by: Keqian Zhu <zhukeqian1@huawei.com>
> > ---
> > Cc: Juan Quintela <quintela@redhat.com>
> > Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > Cc: Eric Blake <eblake@redhat.com>
> > Cc: Markus Armbruster <armbru@redhat.com>
> > ---
>
> > +++ b/qapi/migration.json
> > @@ -524,6 +524,10 @@
> > # compression, so set the decompress-threads to the number about 1/4
> > # of compress-threads is adequate.
> > #
> > +# @throttle-trig-thres: The ratio of bytes_dirty_period and bytes_xfer_period to
> > +# trigger throttling. It is expressed as percentage. The
> > +# default value is 50. (Since 5.0)
> > +#
>
> Abbreviating feels odd; can you please spell this out as
> throttle-trigger-threshold?
>
> Can the threshold exceed 100%?
Note the code checks for that and disallows it, only allowing 1..99
Dave
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3226
> Virtualization: qemu.org | libvirt.org
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-03-12 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 2:57 [PATCH] migration/throttle: Add throttle-trig-thres migration parameter Keqian Zhu
2020-02-21 14:14 ` Eric Blake
2020-02-24 1:11 ` zhukeqian
2020-03-12 17:02 ` Dr. David Alan Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-24 2:31 Keqian Zhu
2020-03-12 18:07 ` Dr. David Alan Gilbert
2020-03-13 3:25 ` zhukeqian
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=20200312170219.GK3211@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wanghaibin.wang@huawei.com \
--cc=zhukeqian1@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).