From: Stefano Garzarella <sgarzare@redhat.com>
To: "Jiang Wang ." <jiang.wang@bytedance.com>
Cc: cong.wang@bytedance.com,
Xiongchun Duan <duanxiongchun@bytedance.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
cohuck@redhat.com, virtualization@lists.linux-foundation.org,
xieyongji@bytedance.com, Stefan Hajnoczi <stefanha@redhat.com>,
asias@redhat.com, Arseny Krasnov <arseny.krasnov@kaspersky.com>
Subject: Re: [External] Re: [RFC PATCH] virtio-vsock: add description for datagram type
Date: Wed, 31 Mar 2021 08:42:36 +0200 [thread overview]
Message-ID: <20210331064236.44h55kysvnfsxeee@steredhat> (raw)
In-Reply-To: <CAP_N_Z956yVDq1P38skH7EXNB-uD_P2tCV=sMYFkUqm2ru4ojw@mail.gmail.com>
On Tue, Mar 30, 2021 at 06:02:33PM -0700, Jiang Wang . wrote:
>Hi Stefano,
>
>I checked dgram code again. I think assigning transport for each packet
>is doable. The dgram will be similar to stream to have two transports.
Yeah, make sense.
>
>If there is no other problem, I can submit a Linux kernel patch to support
>nested dgram on VMCI first. Then it will be easier for virtio vsock.
Okay, I'll look to the patches when you will send.
>
>Also, I don't think we need to put anything related to this multiple-
>transport support in the spec. Let me know if otherwise.
Agree, it's related to the implementation.
Thanks,
Stefano
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-03-31 6:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 21:56 [RFC PATCH] virtio-vsock: add description for datagram type jiang.wang
2021-03-17 15:44 ` Stefan Hajnoczi
2021-03-18 17:59 ` [External] " Jiang Wang .
2021-03-22 16:50 ` Stefan Hajnoczi
2021-03-22 23:02 ` Jiang Wang .
2021-03-22 23:10 ` Michael S. Tsirkin
2021-03-23 2:23 ` Jiang Wang .
2021-03-23 8:53 ` Stefan Hajnoczi
2021-03-26 23:40 ` Jiang Wang .
2021-03-29 9:25 ` Stefan Hajnoczi
2021-03-29 23:22 ` Jiang Wang .
2021-03-30 10:42 ` Stefan Hajnoczi
2021-03-30 18:30 ` Jiang Wang .
2021-03-30 15:32 ` Stefano Garzarella
2021-03-30 18:34 ` Jiang Wang .
2021-03-31 1:02 ` Jiang Wang .
2021-03-31 6:42 ` Stefano Garzarella [this message]
[not found] ` <CAA68J_bQHzFXnsLpCqZ3waPW1NGz+hnu2OXfAG4XOLemLOX9DQ@mail.gmail.com>
2021-04-26 16:07 ` Stefan Hajnoczi
[not found] ` <CAA68J_Z=1uf5rLCpQeH+m9YmsYGsbJgf2VtRJjQrBd_jTdUYuA@mail.gmail.com>
2021-05-13 16:04 ` Stefan Hajnoczi
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=20210331064236.44h55kysvnfsxeee@steredhat \
--to=sgarzare@redhat.com \
--cc=arseny.krasnov@kaspersky.com \
--cc=asias@redhat.com \
--cc=cohuck@redhat.com \
--cc=cong.wang@bytedance.com \
--cc=duanxiongchun@bytedance.com \
--cc=jiang.wang@bytedance.com \
--cc=mst@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
/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