From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] quorum: cleanup and optimization for FIFO case
Date: Fri, 14 Oct 2016 14:51:02 +0100 [thread overview]
Message-ID: <20161014135102.GB3482@stefanha-x1.localdomain> (raw)
In-Reply-To: <1475685327-22767-1-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Wed, Oct 05, 2016 at 06:35:25PM +0200, Paolo Bonzini wrote:
> A couple patches I had lying in the huge multiqueue series but are
> not really related. So let's flush 'em...
>
> Paolo Bonzini (2):
> quorum: change child_iter to children_read
> quorum: do not allocate multiple iovecs for FIFO strategy
>
> block/quorum.c | 93 ++++++++++++++++++++++++++++------------------------------
> 1 file changed, 45 insertions(+), 48 deletions(-)
Kevin: Is this going through your tree?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-10-14 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 16:35 [Qemu-devel] [PATCH 0/2] quorum: cleanup and optimization for FIFO case Paolo Bonzini
2016-10-05 16:35 ` [Qemu-devel] [PATCH 1/2] quorum: change child_iter to children_read Paolo Bonzini
2016-10-05 17:03 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-10-07 12:53 ` [Qemu-devel] " Alberto Garcia
2016-10-05 16:35 ` [Qemu-devel] [PATCH 2/2] quorum: do not allocate multiple iovecs for FIFO strategy Paolo Bonzini
2016-10-05 17:20 ` [Qemu-devel] [Qemu-block] " Max Reitz
2016-10-07 13:01 ` [Qemu-devel] " Alberto Garcia
2016-10-14 13:51 ` Stefan Hajnoczi [this message]
2016-10-17 17:03 ` [Qemu-devel] [Qemu-block] [PATCH 0/2] quorum: cleanup and optimization for FIFO case Max Reitz
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=20161014135102.GB3482@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).