From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, jcody@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] do not use aio_context_acquire/release in AIO-based drivers
Date: Fri, 17 Feb 2017 20:40:25 +0100 [thread overview]
Message-ID: <20170217194028.8398-1-pbonzini@redhat.com> (raw)
aio_context_acquire/release are only going away as soon as the block layer
becomes thread-safe, but we can already move away to other finer-grained
mutex whenever possible.
These three drivers don't use coroutines, hence a QemuMutex is a fine
primitive to use for protecting any per-BDS data in the libraries
they use. The QemuMutex must protect any fd handlers or bottom halves,
and also the BlockDriver callbacks which were implicitly being called
under aio_context_acquire.
Paolo
Paolo Bonzini (3):
curl: do not use aio_context_acquire/release
nfs: do not use aio_context_acquire/release
iscsi: do not use aio_context_acquire/release
block/curl.c | 24 ++++++++++-------
block/iscsi.c | 83 +++++++++++++++++++++++++++++++++++++++++++++--------------
block/nfs.c | 20 +++++++++++---
3 files changed, 95 insertions(+), 32 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-17 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 19:40 Paolo Bonzini [this message]
2017-02-17 19:40 ` [Qemu-devel] [PATCH 1/3] curl: do not use aio_context_acquire/release Paolo Bonzini
2017-02-22 15:13 ` Stefan Hajnoczi
2017-02-17 19:40 ` [Qemu-devel] [PATCH 2/3] nfs: " Paolo Bonzini
2017-02-22 15:13 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-02-17 19:40 ` [Qemu-devel] [PATCH 3/3] iscsi: " Paolo Bonzini
2017-02-22 15:24 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20170217194028.8398-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcody@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).