From: Maxim Levitsky <mlevitsk@redhat.com>
To: Hiroki Narukawa <hnarukaw@yahoo-corp.jp>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
f4bug@amsat.org, hreitz@redhat.com, stefanha@redhat.com,
aoiwa@yahoo-corp.jp
Subject: Re: [PATCH v3 0/1] Patch to adjust coroutine pool size adaptively
Date: Thu, 17 Mar 2022 21:10:48 +0200 [thread overview]
Message-ID: <ce037d5ccd515787dfa0ab47f54bfd0a1756f30f.camel@redhat.com> (raw)
In-Reply-To: <20220128083616.6083-1-hnarukaw@yahoo-corp.jp>
On Fri, 2022-01-28 at 17:36 +0900, Hiroki Narukawa wrote:
> Resending patch with decreasing coroutine pool size on device remove
>
> We encountered random disk IO performance drop since qemu-5.0.0, and this patch fixes it.
>
> Commit message in c740ad92 implied to adjust coroutine pool size adaptively, so I tried to implement this.
>
> Changes from v2:
> Decrease coroutine pool size on device remove
>
> Changes from v1:
> Use qatomic_read properly
>
>
> Hiroki Narukawa (1):
> util: adjust coroutine pool size to virtio block queue
>
> hw/block/virtio-blk.c | 5 +++++
> include/qemu/coroutine.h | 10 ++++++++++
> util/qemu-coroutine.c | 20 ++++++++++++++++----
> 3 files changed, 31 insertions(+), 4 deletions(-)
>
I just bisected this to break my 32 bit qemu setup that I use for testing.
L1 is 32 bit VM with 16 GB of RAM (with PAE) with 16 vCPUs, and
L2 is 32 bit VM with 1.3 GB of RAM and 14 vCPUs (2 less)
Qemu runs out of memory, because new number of coroutines is quite high (14 * 256).
I understand that 32 bit qemu is very limited anyway, so I won't argue
against this patch. Just FYI.
As a workaround I reduced the virtio-blk queue-size to 16
and it seems to work again. I am only keeping this configuration to test
that it boots thus performance is not an issue.
Option to override the coroutine pool size would be ideal in this case IMHO though.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2022-03-17 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 8:36 [PATCH v3 0/1] Patch to adjust coroutine pool size adaptively Hiroki Narukawa
2022-01-28 8:36 ` [PATCH v3 1/1] util: adjust coroutine pool size to virtio block queue Hiroki Narukawa
2022-02-07 17:20 ` Stefan Hajnoczi
2022-02-14 11:54 ` Hiroki Narukawa
2022-02-14 17:11 ` Stefan Hajnoczi
2022-03-17 19:10 ` Maxim Levitsky [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=ce037d5ccd515787dfa0ab47f54bfd0a1756f30f.camel@redhat.com \
--to=mlevitsk@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 \
--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).