All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] thoughts on: virtio: skipping used buffers without IN_ORDER
Date: Wed, 11 Dec 2019 10:33:38 -0500	[thread overview]
Message-ID: <20191211101541-mutt-send-email-mst@kernel.org> (raw)

Hello!
At the moment, if a device uses multiple buffers, it has
to write out a descriptor per buffer. The only exception is
with IN_ORDER where device can skip buffers, with driver
keeping track of IDs.

IN_ORDER is however quite limited in what it can do.  It's not a good
fit for storage, and probably not for RX networking.

It's not hard to extend IN_ORDER so it doesn't apply to specific rings.
A harder question is still writing a single descriptor in this case. One
somewhat easy fix it just to allow descriptors to include multiple IDs.
E.g. address is ignored in used descriptors, we can fit 4 extra IDs in
there. For descriptors where we don't care about the length,
we can stick a couple more IDs on top of that.

I can't say it's all very elegant. Also, is that enough of a win?
We can still end up with multiple descriptors.

More thoughts?

Thanks,
-- 
MST


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/


                 reply	other threads:[~2019-12-11 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191211101541-mutt-send-email-mst@kernel.org \
    --to=mst@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.