From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org,
virtio-comment@lists.oasis-open.org
Subject: [virtio-dev] Re: Virtio BoF minutes from KVM Forum 2017
Date: Wed, 1 Nov 2017 16:59:25 +0200 [thread overview]
Message-ID: <20171101162357-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171029125225.lx4ezpkbvjjsjv3x@localhost.localdomain>
On Sun, Oct 29, 2017 at 01:52:25PM +0100, Jens Freimann wrote:
> Ilya: - you might have more completions than descriptors available
> - partial descriptor chains are a problem for hardware because you might have
> to read a bunch of conscriptors twice - how would you do deal with a big
> buffer that cointains a large number of
> small packets with respect to completions?
> - is one bit for completion enough? right now it means descriptor was actually
> used. how to we signal when it was completed?
I am not sure I understand the difference. Under virtio, driver makes a
descriptor available, then device reads/writes memory depending on
descriptor type, then marks it as used.
What does completed mean?
> - concerned about not being able to do scatter/gatter with the ring layout.
> Network drivers heavily using indirect buffers. - for a hardware
> implementation a completion ring is a very convenient form for
> some use cases, so we want an efficient implementation for them. If we had an
> inline descriptor then a completion ring is just a normal ring and we won't
> need another ring type.
> - doesn't like the fact that we need to do a linear scan to find the length of
> a descriptor chain. It would be nice if we could have the length of the chain
> in the first descriptor (i.e. the number of chained descriptors, not the number
> of posted descriptors which can be deduced from the id field)
Not responding to rest of points since I don't understand the basic
assumption above yet.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2017-11-01 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 12:52 [virtio-dev] Virtio BoF minutes from KVM Forum 2017 Jens Freimann
2017-10-29 12:52 ` Jens Freimann
2017-11-01 14:59 ` Michael S. Tsirkin [this message]
2017-11-01 15:52 ` [virtio-dev] " Ilya Lesokhin
2017-11-01 15:52 ` Ilya Lesokhin
2017-11-01 17:35 ` Michael S. Tsirkin
2017-11-01 17:35 ` [virtio-dev] " Michael S. Tsirkin
2017-11-01 18:12 ` Ilya Lesokhin
2017-11-01 18:12 ` [virtio-dev] " Ilya Lesokhin
2017-11-02 3:40 ` [virtio-dev] " Michael S. Tsirkin
2017-11-02 3:40 ` Michael S. Tsirkin
2017-11-02 8:18 ` Ilya Lesokhin
2017-11-01 14:59 ` Michael S. Tsirkin
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=20171101162357-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jfreimann@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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.