From: Peter Lieven <lieven-lists@dlhnet.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: pbonzini@redhat.com,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] mainloop.c: Keep unlocking BQL during busy-wait spin-out
Date: Thu, 18 Apr 2013 16:22:57 +0200 [thread overview]
Message-ID: <517001C1.8050005@dlhnet.de> (raw)
In-Reply-To: <878v4kvt54.fsf@codemonkey.ws>
On 15.04.2013 15:08, Anthony Liguori wrote:
> Peter Crosthwaite <peter.crosthwaite@xilinx.com> writes:
>
>> Modify Anthony's starvation detection logic to keep the BQL unlocked
>> until the starvation condition goes away. Otherwise the counter has to
>> count up to 1000 for each needed iteration until the busy-wait is
>> lifted.
>>
>> Reset the counter back to zero once glib_pollfds_fill returns with a
>> non-zero timout, (indicating a return to normality). The 1000 iteration
>> wait now only happens once on the transition from normal operation to
>> busy-wait starvation.
>>
>> Anthony's original patch fixed the serial paste bug, but this patch is
>> also needed to restore performance.
>>
>> Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> I'm going through patches for 1.5 candidates.
>
> I believe the paste performance issue has been resolved now and this
> patch is no longer needed. I can't find a definitive statement on the
> list for that though.
I am also hitting a problem that occured first after Anthonys original patch.
In my testing environment I had 3 vServers that indepently of the load became
heavily unresponsive after reporting "main-loop: WARNING: I/O thread spun for 1000 iterations".
Even QMP is not responsing from time to time. But I am not using serial. From the load statistics
it seems that the vServers is using one complete core busy waiting.
I haven't seen this before this patch.
Peter
next prev parent reply other threads:[~2013-04-18 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 5:18 [Qemu-devel] [PATCH] mainloop.c: Keep unlocking BQL during busy-wait spin-out Peter Crosthwaite
2013-04-15 13:08 ` Anthony Liguori
2013-04-15 13:13 ` Paolo Bonzini
2013-04-15 14:39 ` Anthony Liguori
2013-04-18 14:22 ` Peter Lieven [this message]
2013-04-18 14:35 ` Peter Crosthwaite
2013-04-19 7:01 ` Peter Lieven
2013-04-21 14:21 ` Peter Crosthwaite
2013-04-22 8:18 ` Peter Lieven
2013-04-29 11:15 ` Peter Lieven
2013-04-18 14:33 ` Peter Crosthwaite
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=517001C1.8050005@dlhnet.de \
--to=lieven-lists@dlhnet.de \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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.