From: Anthony Liguori <aliguori@us.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] main-loop: drop the BQL if the I/O appears to be spinning
Date: Fri, 05 Apr 2013 10:45:47 -0500 [thread overview]
Message-ID: <87d2u9c76c.fsf@codemonkey.ws> (raw)
In-Reply-To: <515EE7FE.9090202@redhat.com>
Eric Blake <eblake@redhat.com> writes:
> On 04/05/2013 07:46 AM, Anthony Liguori wrote:
>> The char-flow refactoring introduced a busy-wait that depended on
>> an action from the VCPU thread. However, the VCPU thread could
>> never take that action because the busy-wait starved the VCPU thread
>> of the BQL because it never dropped the mutex while running select.
>>
>> Paolo doesn't want to drop this optimization for fear that we will
>> stop detecting these busy waits. I'm afraid to keep this optimization
>> even with the busy-wait fixed because I think a similar problem can
>> occur just with heavy I/O thread load manifesting itself as VCPU pauses.
>>
>> As a compromise, introduce an artificial timeout after a thousand
>> iterations but print a rate limited warning when this happens. This
>> let's us still detect when this condition occurs without it being
>> a fatal error.
>>
>
>> + * print a message to the screen. If we run into this condition, create
>> + * an fake timeout in order to give the VCPU threads a chance to run.
>
> s/an fake/a fake/
Drat, I proof read the commit message hoping to avoid such a mistake but
should have reread the comment :-)
Regards,
Anthony Liguori
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
next prev parent reply other threads:[~2013-04-05 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 13:46 [Qemu-devel] [PATCH] main-loop: drop the BQL if the I/O appears to be spinning Anthony Liguori
2013-04-05 15:04 ` Eric Blake
2013-04-05 15:45 ` Anthony Liguori [this message]
2013-04-05 15:05 ` Paolo Bonzini
2013-04-07 5:12 ` Peter Crosthwaite
2013-04-08 21:55 ` Anthony Liguori
2013-04-09 17:50 ` Andreas Färber
2013-04-09 18:28 ` Anthony Liguori
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=87d2u9c76c.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=eblake@redhat.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 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).