qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] block: three optimizations
Date: Thu, 18 Dec 2014 13:35:07 +0100	[thread overview]
Message-ID: <20141218123507.GC25902@noname.redhat.com> (raw)
In-Reply-To: <1418829000-20288-1-git-send-email-pbonzini@redhat.com>

Am 17.12.2014 um 16:09 hat Paolo Bonzini geschrieben:
> These are three unrelated micro-optimizations of the block layer.
> The first is only visible on non-dataplane operation, the others
> are generic.

Thanks, applied all to the block branch.

Kevin

      parent reply	other threads:[~2014-12-18 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 15:09 [Qemu-devel] [PATCH 0/3] block: three optimizations Paolo Bonzini
2014-12-17 15:09 ` [Qemu-devel] [PATCH 1/3] block: mark AioContext as recursive Paolo Bonzini
2014-12-17 15:09 ` [Qemu-devel] [PATCH 2/3] block: do not allocate an iovec per read of a growable/zero_after_eof BDS Paolo Bonzini
2014-12-17 15:10 ` [Qemu-devel] [PATCH 3/3] block: replace g_new0 with g_new for bottom half allocation Paolo Bonzini
2014-12-18 12:35 ` Kevin Wolf [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=20141218123507.GC25902@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=pbonzini@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).