From: Cornelia Huck <cohuck@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, Halil Pasic <pasic@linux.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: [virtio] Re: [virtio-comment] [PATCH 1/1] split-ring: clarify the field len in the used ring
Date: Mon, 29 Nov 2021 13:23:09 +0100 [thread overview]
Message-ID: <87h7bvi21e.fsf@redhat.com> (raw)
In-Reply-To: <YaSokleLquXepxI4@stefanha-x1.localdomain>
On Mon, Nov 29 2021, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> On Fri, Nov 26, 2021 at 06:12:33PM +0100, Halil Pasic wrote:
>> The current descriptor is misleading: "the descriptor chain which was
>
> s/current descriptor/current description/?
Indeed; easy mistake to make when you look at descriptor chains :)
>
>> used" generally includes both the descriptors that map the device read
>> only, and descriptors that map the device write only portions of the
>> buffer described by the descriptor chain. The argument that "used" means
>> "written to" does not stand because one has to "use" the descriptor
>> chain even when the whole buffer is device read only.
>>
>> One can argue, that the most straightforward way to interpret the phrase
>> "total length of that descriptor chain" (without context) like the
>> length of the list is usually defined: i.e. like the number of
>> descriptors that constitute the chain. This is clearly not what we want
>> here. Another intuitive way to interpret "total length of that
>> descriptor chain" is size of the buffer mapped by the descriptor chain.
>> This is not what we want either. In fact such wrongful interpretations
>> have caused bugs in the wild.
>>
>> On the other hand, the text below the listing that gets modified here
>> clearly describes the semantics of \field{len}. So let us replace
>> the ambiguous explanation in the listing, with a hopefully non-ambiguous
>> one.
>>
>> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
>> ---
>> split-ring.tex | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/split-ring.tex b/split-ring.tex
>> index bfef62d..68dca07 100644
>> --- a/split-ring.tex
>> +++ b/split-ring.tex
>> @@ -402,7 +402,10 @@ \subsection{The Virtqueue Used Ring}\label{sec:Basic Facilities of a Virtio Devi
>> struct virtq_used_elem {
>> /* Index of start of used descriptor chain. */
>> le32 id;
>> - /* Total length of the descriptor chain which was used (written to) */
>> + /*
>> + * The number of bytes written into the device writable portion of
>> + * the buffer described by the descriptor chain.
>> + */
>
> Spaces vs tabs. It looks like 8 spaces should be used here.
Nod.
>
> Otherwise:
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
I can push that with the fixup as an editorial update, if everyone
agrees. (I don't think we need a vote, as the semantics of the field are
already described below.)
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2021-11-29 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 17:12 [PATCH 1/1] split-ring: clarify the field len in the used ring Halil Pasic
2021-11-29 10:16 ` [virtio-comment] " Stefan Hajnoczi
2021-11-29 12:23 ` Cornelia Huck [this message]
2021-11-29 13:04 ` Halil Pasic
2021-11-29 16:32 ` [virtio] " Cornelia Huck
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=87h7bvi21e.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@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