Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>,
	virtio-comment@lists.oasis-open.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>, Greg Kurz <groug@kaod.org>
Subject: [virtio-comment] Re: [PATCH v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC
Date: Tue, 30 Nov 2021 13:06:31 +0100	[thread overview]
Message-ID: <875ys9j1a0.fsf@redhat.com> (raw)
In-Reply-To: <cover.1638192251.git.qemu_oss@crudebyte.com>

On Mon, Nov 29 2021, Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:

> 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]

Now you have me confused: 'revision' is a ccw transport concept, but you
only add support on the pci transport? It's fine to leave out ccw (and
mmio) for now, but you should not talk about revision 3...

>
> 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(-)


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  parent reply	other threads:[~2021-11-30 12:06 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 ` Cornelia Huck [this message]
2021-11-30 13:33   ` [virtio-comment] Re: [PATCH v2 0/2] Add VIRTIO_RING_F_LARGE_INDIRECT_DESC 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=875ys9j1a0.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=groug@kaod.org \
    --cc=qemu_oss@crudebyte.com \
    --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