Re: [PATCH v3 1/1] util: adjust coroutine pool size to virtio block queue

2022-02-14 Thread Stefan Hajnoczi
On Mon, Feb 14, 2022 at 11:54:34AM +, Hiroki Narukawa wrote: > > Coroutine pool size was 64 from long ago, and the basis was organized in the > > commit message in c740ad92. > > Sorry, I noticed that commit ID mentioning here was incorrect. > The correct one is 4d68e86b. > >

RE: [PATCH v3 1/1] util: adjust coroutine pool size to virtio block queue

2022-02-14 Thread Hiroki Narukawa
> Coroutine pool size was 64 from long ago, and the basis was organized in the > commit message in c740ad92. Sorry, I noticed that commit ID mentioning here was incorrect. The correct one is 4d68e86b. https://gitlab.com/qemu-project/qemu/-/commit/4d68e86bb10159099da0798f74e7512955f15eec I have

Re: [PATCH v3 1/1] util: adjust coroutine pool size to virtio block queue

2022-02-07 Thread Stefan Hajnoczi
On Fri, Jan 28, 2022 at 05:36:16PM +0900, Hiroki Narukawa wrote: > Coroutine pool size was 64 from long ago, and the basis was organized in the > commit message in c740ad92. > > At that time, virtio-blk queue-size and num-queue were not configuable, and > equivalent values were 128 and 1. > >

[PATCH v3 1/1] util: adjust coroutine pool size to virtio block queue

2022-01-28 Thread Hiroki Narukawa
Coroutine pool size was 64 from long ago, and the basis was organized in the commit message in c740ad92. At that time, virtio-blk queue-size and num-queue were not configuable, and equivalent values were 128 and 1. Coroutine pool size 64 was fine then. Later queue-size and num-queue got