All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: "Matthias Brugger" <matthias.bgg@gmail.com>,
	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>,
	"Luiz Capitulino" <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Make thread pool implementation modular
Date: Sat, 02 Nov 2013 08:17:18 +0100	[thread overview]
Message-ID: <5274A6FE.1020007@weilnetz.de> (raw)
In-Reply-To: <1383348847-14153-1-git-send-email-matthias.bgg@gmail.com>

Am 02.11.2013 00:34, schrieb Matthias Brugger:
> 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].
>

Please use scripts/checkpatch.pl to check any patch before sending it to
the list.
There are currently errors and warnings for patch 1 and patch 3 which
should be
fixed.

In patch 3 you can also fix "defintion" in the patch description.

Regards,
Stefan

      parent reply	other threads:[~2013-11-02  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 23:34 [Qemu-devel] Make thread pool implementation modular Matthias Brugger
2013-11-01 23:34 ` [Qemu-devel] [PATCH 1/3] " 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 ` Stefan Weil [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=5274A6FE.1020007@weilnetz.de \
    --to=sw@weilnetz.de \
    --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=matthias.bgg@gmail.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 \
    /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.