From: Juan Quintela <quintela@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Malcolm Crossley <malcolm@nutanix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] cpus: reset throttle_thread_scheduled after sleep
Date: Wed, 07 Jun 2017 18:26:39 +0200 [thread overview]
Message-ID: <871sqvepc0.fsf@secure.mitica> (raw)
In-Reply-To: <1495229390-18909-1-git-send-email-felipe@nutanix.com> (Felipe Franciosi's message of "Fri, 19 May 2017 22:29:50 +0100")
Felipe Franciosi <felipe@nutanix.com> wrote:
> Currently, the throttle_thread_scheduled flag is reset back to 0 before
> sleeping (as part of the throttling logic). Given that throttle_timer
> (well, any timer) may tick with a slight delay, it so happens that under
> heavy throttling (ie. close or on CPU_THROTTLE_PCT_MAX) the tick may
> schedule a further cpu_throttle_thread() work item after the flag reset,
> but before the previous sleep completed. This results on the vCPU thread
> sleeping continuously for potentially several seconds in a row.
>
> The chances of that happening can be drastically minimised by resetting
> the flag after the sleep.
>
> Signed-off-by: Felipe Franciosi <felipe@nutanix.com>
> Signed-off-by: Malcolm Crossley <malcolm@nutanix.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Paolo, I think that the analisys makes sense.
Should you pull this patch, or do you want me to pull it?
Thanks, Juan.
next prev parent reply other threads:[~2017-06-07 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 21:29 [Qemu-devel] [PATCH] cpus: reset throttle_thread_scheduled after sleep Felipe Franciosi
2017-05-22 13:01 ` Jason J. Herne
2017-06-01 14:36 ` Dr. David Alan Gilbert
2017-06-01 15:02 ` Felipe Franciosi
2017-06-01 15:08 ` Dr. David Alan Gilbert
2017-05-25 15:52 ` Paolo Bonzini
2017-05-25 16:25 ` Felipe Franciosi
2017-05-25 16:34 ` Paolo Bonzini
2017-06-07 16:26 ` Juan Quintela [this message]
2017-06-07 16:58 ` Paolo Bonzini
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=871sqvepc0.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=felipe@nutanix.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=malcolm@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.