From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
afaerber@suse.de, amit.shah@redhat.com, dgilbert@redhat.com,
borntraeger@de.ibm.com, quintela@redhat.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/5] cpu: Provide vcpu throttling interface
Date: Tue, 01 Sep 2015 10:43:14 -0400 [thread overview]
Message-ID: <55E5B982.2050908@linux.vnet.ibm.com> (raw)
In-Reply-To: <55BC941F.2010906@redhat.com>
On 08/01/2015 05:40 AM, Paolo Bonzini wrote:
>
>
> On 31/07/2015 20:11, Jason J. Herne wrote:
>>>>
>>>
>>> Doh! Yep :). This problem is an artifact of moving the timer_mod from
>>> cpu_throttle_thread into cpu_throttle_timer_tick. I'll have to go back
>>> to the review comments and look at why that was done.
>>
>> So, we made that change in v3 to eliminate the per cpu timer. With a per
>> cpu timer we avoid this problem and we no longer need to worry about
>> a throttle_thread_scheduled, and timers stacking. Paolo, you had originally
>> argued in favor of this change. With what we know now, do you still think
>> having only a single timer is best? Or should I switch back to a timer per
>> cpu? With a timer per cpu we can simply reset the timer immediately after
>> the sleep.
>
> It's okay to have a single timer, only the formulas have to be
> corrected: either you remove the pct/(1-pct) from the callback or you
> add a /(1-pct) to the timer_mod.
>
> Paolo
Paolo,
You are correct here. I've adjusted the timer formula and tested.
Everything seems to be playing nicely now. Sorry it took me a month to
get to this. I got pulled into some critical work and improved
auto-converge took a back seat. I know it is a pain to go back to
something you have not seen in a month so I appreciate any attention
this gets :). A new patch set will be inbound shortly...
--
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)
next prev parent reply other threads:[~2015-09-01 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 16:36 [Qemu-devel] [PATCH v4 0/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 1/5] cpu: Provide vcpu throttling interface Jason J. Herne
2015-07-02 16:43 ` Paolo Bonzini
2015-07-02 16:58 ` Dr. David Alan Gilbert
2015-07-13 14:43 ` Jason J. Herne
2015-07-13 15:14 ` Paolo Bonzini
2015-07-15 12:40 ` Jason J. Herne
2015-07-15 12:54 ` Paolo Bonzini
2015-07-16 14:21 ` Jason J. Herne
2015-07-23 9:59 ` Paolo Bonzini
2015-07-31 17:12 ` Jason J. Herne
2015-07-31 17:16 ` Paolo Bonzini
2015-07-31 17:42 ` Jason J. Herne
2015-07-31 18:11 ` Jason J. Herne
2015-08-01 9:40 ` Paolo Bonzini
2015-09-01 14:43 ` Jason J. Herne [this message]
2015-07-02 16:47 ` Andreas Färber
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 2/5] migration: Parameters for auto-converge cpu throttling Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 3/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 4/5] qmp/hmp: Add throttle ratio to query-migrate and info migrate Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 5/5] migration: Disambiguate MAX_THROTTLE Jason J. Herne
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=55E5B982.2050908@linux.vnet.ibm.com \
--to=jjherne@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@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 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.