qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Utkarsh Tripathi <utkarsh.tripathi@nutanix.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] cpu-throttle: Remove timer_mod() from cpu_throttle_set()
Date: Wed, 3 Feb 2021 08:59:34 +0100	[thread overview]
Message-ID: <a568eb86-3428-ca1e-c2be-e2aa16b6aebd@redhat.com> (raw)
In-Reply-To: <1609420384-119407-1-git-send-email-utkarsh.tripathi@nutanix.com>

On 31/12/20 14:13, Utkarsh Tripathi wrote:
> During migrations, after each iteration, cpu_throttle_set() is called,
> which irrespective of input, re-arms the timer according to value of
> new_throttle_pct. This causes cpu_throttle_thread() to be delayed in
> getting scheduled and consqeuntly lets guest run for more time than what
> the throttle value should allow. This leads to spikes in guest throughput
> at high cpu-throttle percentage whenever cpu_throttle_set() is called.
> 
> A solution would be not to modify the timer immediately in
> cpu_throttle_set(), instead, only modify throttle_percentage so that the
> throttle would automatically adjust to the required percentage when
> cpu_throttle_timer_tick() is invoked.
> 
> Manually tested the patch using following configuration:
> 
> Guest:
> Centos7 (3.10.0-123.el7.x86_64)
> Total Memory - 64GB , CPUs - 16
> Tool used - stress (1.0.4)
> Workload - stress --vm 32 --vm-bytes 1G --vm-keep
> 
> Migration Parameters:
> Network Bandwidth - 500MBPS
> cpu-throttle-initial - 99
> 
> Results:
> With timer_mod(): fails to converge, continues indefinitely
> Without timer_mod(): converges in 249 sec
> 
> Signed-off-by: Utkarsh Tripathi <utkarsh.tripathi@nutanix.com>
> ---
>   softmmu/cpu-throttle.c | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/softmmu/cpu-throttle.c b/softmmu/cpu-throttle.c
> index 2ec4b8e..8c2144a 100644
> --- a/softmmu/cpu-throttle.c
> +++ b/softmmu/cpu-throttle.c
> @@ -90,14 +90,21 @@ static void cpu_throttle_timer_tick(void *opaque)
>   
>   void cpu_throttle_set(int new_throttle_pct)
>   {
> +    /*
> +     * boolean to store whether throttle is already active or not,
> +     * before modifying throttle_percentage
> +     */
> +    bool throttle_active = cpu_throttle_active();
> +
>       /* Ensure throttle percentage is within valid range */
>       new_throttle_pct = MIN(new_throttle_pct, CPU_THROTTLE_PCT_MAX);
>       new_throttle_pct = MAX(new_throttle_pct, CPU_THROTTLE_PCT_MIN);
>   
>       qatomic_set(&throttle_percentage, new_throttle_pct);
>   
> -    timer_mod(throttle_timer, qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL_RT) +
> -                                       CPU_THROTTLE_TIMESLICE_NS);
> +    if (!throttle_active) {
> +        cpu_throttle_timer_tick(NULL);
> +    }
>   }
>   
>   void cpu_throttle_stop(void)
> 

Queued, thanks.

Paolo



      parent reply	other threads:[~2021-02-03  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 13:13 [PATCH] cpu-throttle: Remove timer_mod() from cpu_throttle_set() Utkarsh Tripathi
2021-02-03  5:24 ` Utkarsh Tripathi
2021-02-03  7:59 ` Paolo Bonzini [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=a568eb86-3428-ca1e-c2be-e2aa16b6aebd@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=utkarsh.tripathi@nutanix.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).