From: Matthias Brugger <matthias.bgg@gmail.com>
To: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>, "Alex Bligh" <alex@alex.org.uk>,
malc <av1474@comtv.ru>,
"Liu Ping Fan" <pingfank@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Luiz Capitulino" <lcapitulino@redhat.com>
Subject: [Qemu-devel] Make thread pool implementation modular
Date: Sat, 2 Nov 2013 00:34:04 +0100 [thread overview]
Message-ID: <1383348847-14153-1-git-send-email-matthias.bgg@gmail.com> (raw)
This patch series makes the thread pool implementation modular.
This allows each drive to use a special implementation.
The patch series prepares qemu to be able to include thread pools different
the one actually implemented. It will allow to implement approaches like
paravirtualized block requests [1].
async.c | 4 ++--
block/raw-posix.c | 15 +++++++++++----
block/raw-win32.c | 9 +++++++--
blockdev.c | 13 +++++++++++++
include/block/aio.h | 2 +-
include/block/thread-pool.h | 9 +++++++++
include/qemu-common.h | 2 ++
qemu-options.hx | 2 +-
thread-pool.c | 32 ++++++++++++++++++++++++++++++++
9 files changed, 78 insertions(+), 10 deletions(-)
[1] http://www.linux-kvm.org/wiki/images/5/53/2012-forum-Brugger-lightningtalk.pdf
next reply other threads:[~2013-11-01 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 23:34 Matthias Brugger [this message]
2013-11-01 23:34 ` [Qemu-devel] [PATCH 1/3] Make thread pool implementation modular Matthias Brugger
2013-11-01 23:34 ` [Qemu-devel] [PATCH 2/3] Block layer uses modular thread pool Matthias Brugger
2013-11-01 23:34 ` [Qemu-devel] [PATCH 3/3] Add workerthreads configuration option Matthias Brugger
2013-11-02 7:17 ` [Qemu-devel] Make thread pool implementation modular Stefan Weil
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=1383348847-14153-1-git-send-email-matthias.bgg@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=afaerber@suse.de \
--cc=alex@alex.org.uk \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=av1474@comtv.ru \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).