From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] posix-aio-compat: Fix idle_threads counter
Date: Tue, 3 May 2011 16:56:17 +0100 [thread overview]
Message-ID: <BANLkTikpGRSQ5fp0+GZHCvOyxgq_zhrRJQ@mail.gmail.com> (raw)
In-Reply-To: <1304429178-8782-1-git-send-email-kwolf@redhat.com>
On Tue, May 3, 2011 at 2:26 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> A thread should only be counted as idle when it really is waiting for new
> requests. Without this patch, sometimes too few threads are started as busy
> threads are counted as idle.
>
> Not sure if it makes a difference in practice outside some artificial
> qemu-io/qemu-img tests, but I think the change makes sense in any case.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> posix-aio-compat.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
I think the critical change here is that idle_threads is not being
incremented by spawn_thread(). This means that we will keep spawning
threads as new requests come in and until the first thread goes idle.
Previously you could imagine a scenario where we spawn a thread but
don't schedule it yet. Then we immediately submit more I/O and since
idle_threads was incremented we don't spawn additional threads to
handle the requests.
Are these the cases you were thinking about?
I like your patch because it reduces the number of places where we
mess with idle_threads. I'd move the increment/decrement out of the
loop since the mutex is held here anyway so no one will test
idle_threads between loop iterations, but it's up to you if you want
to send a v2 or not.
Stefan
next prev parent reply other threads:[~2011-05-03 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 13:26 [Qemu-devel] [PATCH] posix-aio-compat: Fix idle_threads counter Kevin Wolf
2011-05-03 15:56 ` Stefan Hajnoczi [this message]
2011-05-03 16:53 ` Kevin Wolf
2011-05-04 7:41 ` Stefan Hajnoczi
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=BANLkTikpGRSQ5fp0+GZHCvOyxgq_zhrRJQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=kwolf@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).