From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org
Subject: [PULL 0/1] Block patches
Date: Thu, 21 Oct 2021 18:41:03 +0100 [thread overview]
Message-ID: <20211021174104.52826-1-stefanha@redhat.com> (raw)
The following changes since commit afc9fcde55296b83f659de9da3cdf044812a6eeb:
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2021-10-20 06:10:51 -0700)
are available in the Git repository at:
https://gitlab.com/stefanha/qemu.git tags/block-pull-request
for you to fetch changes up to 4b2b3d2653f255ef4259a7689af1956536565901:
coroutine: resize pool periodically instead of limiting size (2021-10-21 18:40:07 +0100)
----------------------------------------------------------------
Pull request
Performance optimization when guest applications submit a lot of parallel I/O.
This has also been found to improve clang SafeStack performance.
----------------------------------------------------------------
Stefan Hajnoczi (1):
coroutine: resize pool periodically instead of limiting size
include/qemu/coroutine-pool-timer.h | 36 ++++++++++++++++
include/qemu/coroutine.h | 7 ++++
iothread.c | 6 +++
util/coroutine-pool-timer.c | 35 ++++++++++++++++
util/main-loop.c | 5 +++
util/qemu-coroutine.c | 64 ++++++++++++++++-------------
util/meson.build | 1 +
7 files changed, 125 insertions(+), 29 deletions(-)
create mode 100644 include/qemu/coroutine-pool-timer.h
create mode 100644 util/coroutine-pool-timer.c
--
2.31.1
next reply other threads:[~2021-10-21 17:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 17:41 Stefan Hajnoczi [this message]
2021-10-21 17:41 ` [PULL 1/1] coroutine: resize pool periodically instead of limiting size Stefan Hajnoczi
2021-10-21 22:08 ` [PULL 0/1] Block patches Richard Henderson
2021-10-25 10:10 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2024-04-29 13:43 Stefan Hajnoczi
2024-03-19 15:09 Stefan Hajnoczi
2024-03-19 19:11 ` Peter Maydell
2024-02-06 15:31 Stefan Hajnoczi
2024-02-07 22:19 ` Kevin Wolf
2023-10-16 19:40 Stefan Hajnoczi
2023-10-04 13:53 Stefan Hajnoczi
2023-10-04 18:33 ` Stefan Hajnoczi
2023-07-12 19:36 Stefan Hajnoczi
2023-07-14 6:35 ` Richard Henderson
2023-07-04 15:29 Stefan Hajnoczi
2023-07-06 6:04 ` Richard Henderson
2022-09-22 17:14 Stefan Hajnoczi
2022-09-27 15:04 ` Stefan Hajnoczi
2022-05-25 12:49 Stefan Hajnoczi
2022-05-25 18:35 ` Richard Henderson
2021-12-09 15:21 Stefan Hajnoczi
2021-12-09 15:46 ` Peter Maydell
2021-12-09 16:34 ` Stefan Hajnoczi
2021-12-09 16:53 ` Richard Henderson
2021-12-13 9:33 ` Stefan Hajnoczi
2021-12-14 22:31 ` Richard Henderson
2021-12-06 15:27 Stefan Hajnoczi
2021-12-06 21:16 ` Richard Henderson
2021-03-15 9:51 Stefan Hajnoczi
2021-03-15 22:01 ` Peter Maydell
2021-01-04 14:23 Stefan Hajnoczi
2021-01-04 17:17 ` Peter Maydell
2020-03-17 15:18 Stefan Hajnoczi
2020-03-17 18:32 ` Peter Maydell
2020-01-14 9:30 Stefan Hajnoczi
2020-01-14 16:00 ` Peter Maydell
2019-10-14 8:52 Stefan Hajnoczi
2019-10-15 11:00 ` Peter Maydell
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=20211021174104.52826-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.