From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
virtio-comment@lists.oasis-open.org, Greg Kurz <groug@kaod.org>
Subject: Re: [virtio-comment] Re: [PATCH v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC
Date: Thu, 09 Dec 2021 13:33:20 +0100 [thread overview]
Message-ID: <2346601.RvB5glhVSD@silver> (raw)
In-Reply-To: <877dcft8u0.fsf@redhat.com>
On Mittwoch, 8. Dezember 2021 16:28:07 CET Cornelia Huck wrote:
> On Wed, Dec 08 2021, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > On Wed, Dec 08, 2021 at 01:26:54PM +0100, Christian Schoenebeck wrote:
> >> One more thought: what about making the new 'queue_indirect_size' config
> >> field 32 bit wide instead of 16 bit? That would easily mitigate the
> >> issue of the aggregated limit discussed here, and would in general be
> >> more future safe, i.e. considering that there might be either
> >> nested/multi-level indirect descriptor tables or chained tables in
> >> future? The cost would be low, right?>
> > The MMIO transport has 32-bit fields, so there doesn't seem to be a
> > strict requirement to use 16 bits for descriptor counts.
> >
> > I think you're right that the cost is low. Usually it's the access
> > itself that carries a cost (a VM exit or bus transaction) and 2 vs 4
> > byte transfers don't really matter.
>
> For ccw, I think we'd simply include the value in a control block, and
> it does not really matter whether that control block is 2 bytes
> longer. So, no objection from me.
Sounds like a plan!
I will send a new version next week. Thanks guys!
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2021-12-09 12:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 13:24 [PATCH v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC Christian Schoenebeck
2021-11-29 13:22 ` [PATCH v2 1/2] " Christian Schoenebeck
2021-12-02 16:04 ` Stefan Hajnoczi
2021-11-29 13:23 ` [PATCH v2 2/2] Add common configuration field "queue_indirect_size" Christian Schoenebeck
2021-12-02 16:21 ` Stefan Hajnoczi
2021-12-03 15:03 ` Christian Schoenebeck
2021-12-06 13:54 ` Stefan Hajnoczi
2021-11-30 12:06 ` [virtio-comment] Re: [PATCH v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC Cornelia Huck
2021-11-30 13:33 ` Christian Schoenebeck
2021-11-30 13:48 ` Cornelia Huck
2021-11-30 18:47 ` Christian Schoenebeck
2021-12-02 10:27 ` Cornelia Huck
2021-12-03 14:47 ` Christian Schoenebeck
2021-12-06 11:52 ` Cornelia Huck
2021-12-06 19:12 ` Christian Schoenebeck
2021-12-07 9:50 ` Stefan Hajnoczi
2021-12-07 18:00 ` Cornelia Huck
2021-12-08 12:26 ` Christian Schoenebeck
2021-12-08 15:11 ` Stefan Hajnoczi
2021-12-08 15:28 ` Cornelia Huck
2021-12-09 12:33 ` Christian Schoenebeck [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=2346601.RvB5glhVSD@silver \
--to=qemu_oss@crudebyte.com \
--cc=cohuck@redhat.com \
--cc=groug@kaod.org \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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