Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: mst@redhat.com, stefanha@redhat.com,
	virtio-comment@lists.oasis-open.org,
	arseny.krasnov@kaspersky.com, jasowang@redhat.com
Subject: [virtio-comment] Re: [PATCH v11 0/3] virtio-vsock: SOCK_SEQPACKET description
Date: Thu, 13 Jan 2022 15:06:54 +0100	[thread overview]
Message-ID: <877db3wwzl.fsf@redhat.com> (raw)
In-Reply-To: <20220113135758.nifr7hftqh57viku@steredhat>

On Thu, Jan 13 2022, Stefano Garzarella <sgarzare@redhat.com> wrote:

> On Thu, Jan 13, 2022 at 12:34:20PM +0100, Cornelia Huck wrote:
>>> Otherwise maybe we should write in the spec that if F_SEQPACKET is set
>>> this means that stream is supported even if F_STREAM is not set.
>>
>>Yes, if that works, it would probably be the less ugly option.
>
> Okay, let's go for F_STREAM (even Michael's comment seems to agree with 
> that).
>
> Do you think we need to write this implication into the specification, 
> or do we leave it to the implementation to solve this transient problem?

I would add something like "if F_SEQPACKET has been negotiated, the
[device|driver] MUST act as if F_STREAM has also been negotiated".


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-01-13 14:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 17:09 [PATCH v11 0/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 1/3] virtio-vsock: use C style defines for constants Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 2/3] virtio-vsock: add VIRTIO_VSOCK_F_STREAM feature bit Stefano Garzarella
2022-01-12 17:09 ` [PATCH v11 3/3] virtio-vsock: SOCK_SEQPACKET description Stefano Garzarella
2022-01-13 10:50 ` [virtio-comment] Re: [PATCH v11 0/3] " Cornelia Huck
2022-01-13 11:22   ` Stefano Garzarella
2022-01-13 11:34     ` [virtio-comment] " Cornelia Huck
2022-01-13 13:57       ` Stefano Garzarella
2022-01-13 14:06         ` Cornelia Huck [this message]
2022-01-13 14:16           ` [virtio-comment] " Stefano Garzarella
2022-01-13 15:11           ` Michael S. Tsirkin
2022-01-13 16:33             ` Stefano Garzarella
2022-01-13 13:19   ` Michael S. Tsirkin
2022-01-13 13:52 ` Stefano Garzarella

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=877db3wwzl.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=arseny.krasnov@kaspersky.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@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