All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC
Date: Mon, 29 Nov 2021 14:24:11 +0100	[thread overview]
Message-ID: <cover.1638192251.git.qemu_oss@crudebyte.com> (raw)

This is a follow-up of:
https://lists.oasis-open.org/archives/virtio-comment/202111/msg00059.html

These two patches introduce a more fine graded control over the maximum
length of an indirect descriptor table.

Associated Github Task:
https://github.com/oasis-tcs/virtio-spec/issues/122

v1 -> v2:

  * "active/pending message(s)" -> "vring slot(s)"
    NOTE: I decided to use the term "vring slot(s)" over the previously
    suggested term "buffer(s)" as I found tha latter too ambiguous in this
    context. [patch 1]

  * "... but does not oppose a limit to the actual bulk data size
    being transmitted."
    ->
    " ... but does not oppose a limit to the actual bulk data size
    being transmitted when indirect descriptors are used." [patch 1]

  * Add common configuration field "queue_indirect_size" and make it
    mandatory as of revision 3. [NEW patch 2]

Christian Schoenebeck (2):
  Add VIRTIO_RING_F_LARGE_INDIRECT_DESC
  Add common configuration field "queue_indirect_size"

 content.tex    | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++
 split-ring.tex |  7 ++++++-
 2 files changed, 62 insertions(+), 1 deletion(-)

-- 
2.20.1


             reply	other threads:[~2021-11-29 13:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 13:24 Christian Schoenebeck [this message]
2021-11-29 13:22 ` [PATCH v2 1/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC 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

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.1638192251.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.