From: Kevin Wolf <kwolf@redhat.com>
To: "成川 弘樹" <hnarukaw@yahoo-corp.jp>
Cc: qemu-block@nongnu.org, stefanha@redhat.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH 2/2] coroutine: Revert to constant batch size
Date: Thu, 12 May 2022 11:57:17 +0200 [thread overview]
Message-ID: <YnzZ/eedEb9j+VHE@redhat.com> (raw)
In-Reply-To: <41c8f1d4-be27-4110-33c0-b53a701a9cb6@yahoo-corp.jp>
Am 12.05.2022 um 08:56 hat 成川 弘樹 geschrieben:
> Thank you for your fix.
>
> I confirmed that after applying this patch, my intended performance
> improvement by 4c41c69e is still kept in our environment.
This is good news. Thank you for testing the patch!
Kevin
next prev parent reply other threads:[~2022-05-12 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:10 [PATCH 0/2] coroutine: Fix crashes due to too large pool batch size Kevin Wolf
2022-05-10 15:10 ` [PATCH 1/2] coroutine: Rename qemu_coroutine_inc/dec_pool_size() Kevin Wolf
2022-05-10 15:10 ` [PATCH 2/2] coroutine: Revert to constant batch size Kevin Wolf
2022-05-12 6:56 ` 成川 弘樹
2022-05-12 9:57 ` Kevin Wolf [this message]
2022-05-12 12:50 ` Philippe Mathieu-Daudé via
2022-05-13 1:18 ` 成川 弘樹
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=YnzZ/eedEb9j+VHE@redhat.com \
--to=kwolf@redhat.com \
--cc=hnarukaw@yahoo-corp.jp \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).