From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for 2.1 0/4] AioContext cleanups and optimizations
Date: Tue, 8 Jul 2014 17:11:41 +0200 [thread overview]
Message-ID: <20140708151141.GF3857@noname.str.redhat.com> (raw)
In-Reply-To: <1404739084-3783-1-git-send-email-pbonzini@redhat.com>
Am 07.07.2014 um 15:18 hat Paolo Bonzini geschrieben:
> These patches do some cleanup and optimization in AioContext land.
>
> The first two drop AIO functions that operate on the main AioContext.
> These are not needed anymore now that each BlockDriverState explicitly
> operates on its own AioContext. They are independent, and can be
> skipped if the maintainers prefer doing so or have comments.
>
> Patch 3 is a testsuite change for the aio_notify optimization, and
> patch 4 is the aio_notify patch, now with a better comment
> about the smp_mb optimization.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2014-07-08 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 13:18 [Qemu-devel] [PATCH for 2.1 0/4] AioContext cleanups and optimizations Paolo Bonzini
2014-07-07 13:18 ` [Qemu-devel] [PATCH 1/4] block: prefer aio_poll to qemu_aio_wait Paolo Bonzini
2014-07-07 13:18 ` [Qemu-devel] [PATCH 2/4] block: drop aio functions that operate on the main AioContext Paolo Bonzini
2014-07-07 13:18 ` [Qemu-devel] [PATCH 3/4] test-aio: fix GSource-based timer test Paolo Bonzini
2014-07-07 13:18 ` [Qemu-devel] [PATCH 4/4] AioContext: speed up aio_notify Paolo Bonzini
2014-07-08 15:11 ` 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=20140708151141.GF3857@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=pbonzini@redhat.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 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).