From: "Michael S. Tsirkin" <mst@redhat.com>
To: Laura Loghin <lauralg@amazon.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
virtio-comment@lists.oasis-open.org,
Cornelia Huck <cohuck@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [virtio-comment] [PATCH v4] virtio-vsock: add max payload size config field
Date: Mon, 27 Jun 2022 11:20:18 -0400 [thread overview]
Message-ID: <20220627111907-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0ce9b731-ba35-6b0d-a66e-976da2966e54@amazon.com>
On Mon, Jun 27, 2022 at 04:33:27PM +0300, Laura Loghin wrote:
> > > > There are sections in the spec that make you think of a buffer as
> > > > corresponding to a descriptor chain, and others that don't, for example:
> > > > 2.6.5 The Virtqueue Descriptor Table: Each descriptor describes a
> > > > buffer which is read-only for the device (“device-readable”) or
> > > > write-only for the device (“device-writable”), but a chain of descriptors
> > > > can contain both device-readable and device-writable buffers.
I think this should just refer to memory:
Each descriptor describes
memory which is read-only for the device (``device-readable'') or write-only for the device (``device-writable''), but a chain of
descriptors can contain both device-readable and device-writable memory.
next prev parent reply other threads:[~2022-06-27 15:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 10:40 [virtio-comment] [PATCH v4] virtio-vsock: add max payload size config field Laura Loghin
2022-06-13 11:50 ` Cornelia Huck
2022-06-13 12:51 ` Stefano Garzarella
2022-06-14 11:57 ` Halil Pasic
2022-06-16 16:40 ` Michael S. Tsirkin
2022-06-20 9:43 ` Cornelia Huck
2022-06-20 9:47 ` Laura Loghin
2022-06-20 10:13 ` Michael S. Tsirkin
2022-06-20 10:18 ` Laura Loghin
2022-06-20 11:20 ` Cornelia Huck
2022-06-20 13:07 ` Laura Loghin
2022-06-20 13:29 ` Cornelia Huck
2022-06-24 9:53 ` Laura Loghin
2022-06-23 15:36 ` Laura Loghin
2022-06-23 16:22 ` Michael S. Tsirkin
2022-06-24 8:23 ` Laura Loghin
2022-06-27 12:59 ` Halil Pasic
2022-06-27 13:15 ` Michael S. Tsirkin
2022-06-27 13:33 ` Laura Loghin
2022-06-27 15:20 ` Michael S. Tsirkin [this message]
2022-06-23 15:11 ` Laura Loghin
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=20220627111907-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=lauralg@amazon.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@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.