From: Stefan Hajnoczi <stefanha@redhat.com>
To: Hiroki Narukawa <hnarukaw@yahoo-corp.jp>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>,
"f4bug@amsat.org" <f4bug@amsat.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"hreitz@redhat.com" <hreitz@redhat.com>,
Akira Oiwa <aoiwa@yahoo-corp.jp>
Subject: Re: [PATCH 0/1 v2] Patch to adjust coroutine pool size adaptively
Date: Wed, 26 Jan 2022 15:38:46 +0000 [thread overview]
Message-ID: <YfFrBmi3aXD5ChVn@stefanha-x1.localdomain> (raw)
In-Reply-To: <TYCPR01MB83573704C604BC31B157B3EA805E9@TYCPR01MB8357.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
On Mon, Jan 24, 2022 at 10:01:30AM +0000, Hiroki Narukawa wrote:
> ping, how is the status of this patch?
>
> Link for this patch v2 on patchew is this one: https://patchew.org/QEMU/20220111091950.840-1-hnarukaw@yahoo-corp.jp/
> The last message on patch v1 is this one: https://lore.kernel.org/qemu-devel/TYCPR01MB8357E8D13D661265CDBB442C80519@TYCPR01MB8357.jpnprd01.prod.outlook.com/T/#u
>
> The difference from v1 is use of qatomic_read().
Hi,
Sorry for the slow response. I will review this tomorrow (Thursday)!
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-26 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:19 [PATCH 0/1 v2] Patch to adjust coroutine pool size adaptively Hiroki Narukawa
2022-01-11 9:19 ` [PATCH 1/1] util: adjust coroutine pool size to virtio block queue Hiroki Narukawa
2022-01-27 15:47 ` Stefan Hajnoczi
2022-01-28 8:50 ` Hiroki Narukawa
2022-01-24 10:01 ` [PATCH 0/1 v2] Patch to adjust coroutine pool size adaptively Hiroki Narukawa
2022-01-26 15:38 ` Stefan Hajnoczi [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=YfFrBmi3aXD5ChVn@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=aoiwa@yahoo-corp.jp \
--cc=f4bug@amsat.org \
--cc=hnarukaw@yahoo-corp.jp \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@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).