Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Laura Loghin <lauralg@amazon.com>,
	Stefano Garzarella <sgarzare@redhat.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH] vsock: add documentation about len header field
Date: Wed, 06 Apr 2022 10:32:46 +0200	[thread overview]
Message-ID: <878rsifw7l.fsf@redhat.com> (raw)
In-Reply-To: <dafc9518-ef57-f659-14b1-b14890017f46@amazon.com>

On Tue, Mar 29 2022, Laura Loghin <lauralg@amazon.com> wrote:

> On 3/28/22 14:09, Stefano Garzarella wrote:
>> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>>
>>
>>
>> Hi Laura,
>>
>> On Tue, Mar 22, 2022 at 10:50 AM Laura Loghin<lauralg@amazon.com>  wrote:
>>> Signed-off-by: Laura Loghin<lauralg@amazon.com>
>>> ---
>>>   virtio-vsock.tex | 5 +++++
>>>   1 file changed, 5 insertions(+)
>>>
>>> diff --git a/virtio-vsock.tex b/virtio-vsock.tex
>>> index d79984d..e32cad8 100644
>>> --- a/virtio-vsock.tex
>>> +++ b/virtio-vsock.tex
>>> @@ -107,6 +107,11 @@ \subsection{Device Operation}\label{sec:Device Types / Socket Device / Device Op
>>>   #define VIRTIO_VSOCK_OP_CREDIT_REQUEST 7
>>>   \end{lstlisting}
>>>
>>> +\field{len} is the size of the payload, in bytes. However, the driver may
>>> +provide buffer(s) for the payload that have a total size longer than
>>> +\field{len}. If that is the case, only the first \field{len} bytes MUST be
>>> +used for the actual data.
>>> +
>> IIUC MUST and friends are for normative sections, so I would remove
>> the last sentence.
>
> You're right, I'll remove it. It should already be clear enough only the
> first len bytes need to be used for the payload.

Another option would be

"However, the driver may provide buffer(s) for the payload that have a
total size longer than \field{len}, in which case only the first
\field{len} bytes will be used for the actual data."


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:[~2022-04-06  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  9:49 [virtio-comment] [PATCH] vsock: add documentation about len header field Laura Loghin
2022-03-28 11:09 ` Stefano Garzarella
2022-03-29 14:24   ` Laura Loghin
2022-04-06  8:32     ` Cornelia Huck [this message]
2022-04-07  8:16       ` 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=878rsifw7l.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=lauralg@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox