All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] block IO thread creation question
Date: Fri, 25 Mar 2016 10:25:47 +0800	[thread overview]
Message-ID: <20160325022547.GE29171@ad.usersys.redhat.com> (raw)
In-Reply-To: <56F4017D.7040502@windriver.com>

On Thu, 03/24 09:02, Chris Friesen wrote:
> Hi,
> 
> Could someone point me at the code for creating threads to handle
> block IO?  I'm seeing up to 30 threads per virtual disk, which seems
> high.

It is thread-pool.c, assuming you are using "aio=threads" for drive, which is
the default. With the alternative, "aio=native", spawning worker threads will
be much more uncommon.

Fam

> 
> In case it's related, the block devices are iSCSI with the host
> acting as the initiator and exposing block devices to qemu.
> 
> I'm particularly interested in qemu 2.2, just in case things have
> changed significantly since then.
> 
> Thanks,
> Chris
> 

      reply	other threads:[~2016-03-25  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 15:02 [Qemu-devel] block IO thread creation question Chris Friesen
2016-03-25  2:25 ` Fam Zheng [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=20160325022547.GE29171@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=chris.friesen@windriver.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.