[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k
From: |
Christian Schoenebeck |
Subject: |
Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k |
Date: |
Wed, 10 Nov 2021 16:53:33 +0100 |
On Mittwoch, 10. November 2021 16:14:19 CET Stefan Hajnoczi wrote:
> On Wed, Nov 10, 2021 at 02:14:43PM +0100, Christian Schoenebeck wrote:
> > On Mittwoch, 10. November 2021 11:05:50 CET Stefan Hajnoczi wrote:
> > As you are apparently reluctant for changing the virtio specs, what about
> > introducing those discussed virtio capabalities either as experimental
> > ones
> > without specs changes, or even just as 9p specific device capabilities for
> > now. I mean those could be revoked on both sides at any time anyway.
>
> I would like to understand the root cause before making changes.
>
> "It's faster when I do X" is useful information but it doesn't
> necessarily mean doing X is the solution. The "it's faster when I do X
> because Y" part is missing in my mind. Once there is evidence that shows
> Y then it will be clearer if X is a good solution, if there's a more
> general solution, or if it was just a side-effect.
I think I made it clear that the root cause of the observed performance gain
with rising transmission size is latency (and also that performance is not the
only reason for addressing this queue size issue).
Each request roundtrip has a certain minimum latency, the virtio ring alone
has its latency, plus latency of the controller portion of the file server
(e.g. permissions, sandbox checks, file IDs) that is executed with *every*
request, plus latency of dispatching the request handling between threads
several times back and forth (also for each request).
Therefore when you split large payloads (e.g. reading a large file) into
smaller n amount of chunks, then that individual latency per request
accumulates to n times the individual latency, eventually leading to degraded
transmission speed as those requests are serialized.
> I'm sorry for frustrating your efforts here. We have discussed a lot of
> different ideas and maybe our perspectives are not that far apart
> anymore.
>
> Keep going with what you think is best. If I am still skeptical we can
> ask someone else to review the patches instead of me so you have a
> second opinion.
>
> Stefan
Thanks Stefan!
In the meantime I try to address your objections as far as I can. If there is
more I can do (with reasonable effort) to resolve your doubts, just let me
know.
Best regards,
Christian Schoenebeck
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/01
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/03
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/04
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/09
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/09
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/10
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/10
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/10
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k,
Christian Schoenebeck <=
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/11
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/11
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/15
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Christian Schoenebeck, 2021/11/15
- Re: [PATCH v2 0/3] virtio: increase VIRTQUEUE_MAX_SIZE to 32k, Stefan Hajnoczi, 2021/11/16