From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: virtio-comment@lists.oasis-open.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Cornelia Huck <cohuck@redhat.com>, Greg Kurz <groug@kaod.org>
Subject: [PATCH 0/2] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size
Date: Tue, 14 Dec 2021 16:13:23 +0100 [thread overview]
Message-ID: <cover.1639494803.git.qemu_oss@crudebyte.com> (raw)
This is a follow-up of:
[0/2]: https://lists.oasis-open.org/archives/virtio-comment/202111/msg00089.html
[1/2]: https://lists.oasis-open.org/archives/virtio-comment/202112/msg00005.html
[2/2]: https://lists.oasis-open.org/archives/virtio-comment/202112/msg00006.html
These two patches introduce a more fine graded control over the maximum length
of indirect descriptor tables.
Associated Github Task:
https://github.com/oasis-tcs/virtio-spec/issues/122
Changes:
* VIRTIO_RING_F_LARGE_INDIRECT_DESC -> VIRTIO_RING_F_INDIRECT_SIZE
[patch 1], [patch 2]
* queue_indirect_size field: 16 bit -> 32 bit [patch 2]
* Semantic change: "per indirect descriptor table" -> "per vring slot".
[patch 2]
* Revised first paragraph of VIRTIO_RING_F_INDIRECT_SIZE(40) to be more clear
that it is not only about exceeding the queue size
("This feature indicates ... "). [patch 1]
* Drop mentioning "revision 3". [patch 2]
* revised commit log [patch 1]
* Grammar: "... but does not limit the actual bulk data size ...". [patch 1]
* Grammar: "... if the device ...". [patch 1]
* queue_indirect_size field may only be used if VIRTIO_RING_F_INDIRECT_SIZE
was used. [patch 2]
* Drop usage of SHOULD/MUST in common description. [patch 2]
* Grammar: had been -> was [patch 2]
* Add requirements for field 'queue_indirect_size' to driver normative
section. [patch 2]
Christian Schoenebeck (2):
Add VIRTIO_RING_F_INDIRECT_SIZE
Add common configuration field "queue_indirect_size"
content.tex | 44 ++++++++++++++++++++++++++++++++++++++++++++
split-ring.tex | 5 ++++-
2 files changed, 48 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2021-12-14 15:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 15:13 Christian Schoenebeck [this message]
2021-12-14 15:13 ` [PATCH 1/2] Add VIRTIO_RING_F_INDIRECT_SIZE Christian Schoenebeck
2021-12-14 16:59 ` [virtio-comment] " Cornelia Huck
2021-12-14 18:28 ` Christian Schoenebeck
2021-12-23 10:54 ` Cornelia Huck
2022-01-24 13:08 ` Stefan Hajnoczi
2022-01-24 13:14 ` [virtio-comment] " Cornelia Huck
2022-01-24 14:24 ` Christian Schoenebeck
2021-12-14 15:13 ` [PATCH 2/2] Add common configuration field "queue_indirect_size" Christian Schoenebeck
2021-12-14 17:20 ` [virtio-comment] " Cornelia Huck
2021-12-15 13:59 ` Christian Schoenebeck
2021-12-23 11:03 ` [virtio-comment] " Cornelia Huck
2021-12-29 14:16 ` Christian Schoenebeck
2022-01-03 13:21 ` [virtio-comment] " Cornelia Huck
2022-01-05 13:52 ` Christian Schoenebeck
2022-01-24 13:39 ` [virtio-comment] " Stefan Hajnoczi
2022-01-24 14:31 ` Christian Schoenebeck
2022-01-24 16:41 ` Stefan Hajnoczi
2022-01-25 19:05 ` Christian Schoenebeck
2022-01-26 10:01 ` Stefan Hajnoczi
2022-01-24 13:53 ` Stefan Hajnoczi
2022-02-19 16:36 ` Christian Schoenebeck
2022-02-21 10:33 ` Stefan Hajnoczi
2022-02-21 13:28 ` Christian Schoenebeck
2022-01-24 13:54 ` [PATCH 0/2] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size Stefan Hajnoczi
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=cover.1639494803.git.qemu_oss@crudebyte.com \
--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