From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
Stefan Weil <sw@weilnetz.de>,
Stefan Hajnoczi <stefanha@redhat.com>, Fam Zheng <fam@euphon.net>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Subject: [PATCH 0/2] AioContext removal: LinuxAioState and ThreadPool
Date: Thu, 9 Jun 2022 09:44:50 -0400 [thread overview]
Message-ID: <20220609134452.1146309-1-eesposit@redhat.com> (raw)
Just remove some AioContext lock in LinuxAioState and ThreadPool.
Not related to anything specific, so I decided to send it as
a separate patch.
These patches are taken from Paolo's old draft series.
Emanuele Giuseppe Esposito (1):
thread-pool: use ThreadPool from the running thread
Paolo Bonzini (1):
linux-aio: use LinuxAioState from the running thread
block/file-posix.c | 22 +++++++++++-----------
block/file-win32.c | 2 +-
block/linux-aio.c | 13 ++++++-------
block/qcow2-threads.c | 2 +-
include/block/aio.h | 4 ----
util/thread-pool.c | 6 +-----
6 files changed, 20 insertions(+), 29 deletions(-)
--
2.31.1
next reply other threads:[~2022-06-09 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 13:44 Emanuele Giuseppe Esposito [this message]
2022-06-09 13:44 ` [PATCH 1/2] linux-aio: use LinuxAioState from the running thread Emanuele Giuseppe Esposito
2022-09-29 14:52 ` Kevin Wolf
2022-09-30 10:00 ` Emanuele Giuseppe Esposito
2022-09-30 15:32 ` Kevin Wolf
2022-10-03 9:18 ` Emanuele Giuseppe Esposito
2022-06-09 13:44 ` [PATCH 2/2] thread-pool: use ThreadPool " Emanuele Giuseppe Esposito
2022-09-29 15:30 ` Kevin Wolf
2022-09-30 12:17 ` Emanuele Giuseppe Esposito
2022-09-30 14:46 ` Emanuele Giuseppe Esposito
2022-09-30 15:45 ` Kevin Wolf
2022-10-03 8:52 ` Emanuele Giuseppe Esposito
2022-10-20 15:39 ` Stefan Hajnoczi
2022-10-20 16:22 ` Dr. David Alan Gilbert
2022-10-24 18:49 ` 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=20220609134452.1146309-1-eesposit@redhat.com \
--to=eesposit@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).