[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FE66B72-E16B-474D-9A17-70B3BCCD5A19@vmware.com>
Date: Tue, 13 Apr 2021 09:02:22 +0000
From: Jorgen Hansen <jhansen@...are.com>
To: "Jiang Wang ." <jiang.wang@...edance.com>
CC: "virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Stefan Hajnoczi <stefanha@...hat.com>,
"cong.wang@...edance.com" <cong.wang@...edance.com>,
"duanxiongchun@...edance.com" <duanxiongchun@...edance.com>,
"xieyongji@...edance.com" <xieyongji@...edance.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Stefano Garzarella <sgarzare@...hat.com>,
Colin Ian King <colin.king@...onical.com>,
Norbert Slusarek <nslusarek@....net>,
Andra Paraschiv <andraprs@...zon.com>,
Alexander Popov <alex.popov@...ux.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [External] [RFC] vsock: add multiple transports support for dgram
> On 7 Apr 2021, at 20:25, Jiang Wang . <jiang.wang@...edance.com> wrote:
>
> On Wed, Apr 7, 2021 at 2:51 AM Jorgen Hansen <jhansen@...are.com> wrote:
>>
>>
>>> On 6 Apr 2021, at 20:31, Jiang Wang <jiang.wang@...edance.com> wrote:
>>>
>>> From: "jiang.wang" <jiang.wang@...edance.com>
>>>
>>> Currently, only VMCI supports dgram sockets. To supported
>>> nested VM use case, this patch removes transport_dgram and
>>> uses transport_g2h and transport_h2g for dgram too.
>>
>> Could you provide some background for introducing this change - are you
>> looking at introducing datagrams for a different transport? VMCI datagrams
>> already support the nested use case,
>
> Yes, I am trying to introduce datagram for virtio transport. I wrote a
> spec patch for
> virtio dgram support and also a code patch, but the code patch is still WIP.
Oh ok. Cool. I must have missed the spec patch - could you provide a reference to
it?
> When I wrote this commit message, I was thinking nested VM is the same as
> multiple transport support. But now, I realize they are different.
> Nested VMs may use
> the same virtualization layer(KVM on KVM), or different virtualization layers
> (KVM on ESXi). Thanks for letting me know that VMCI already supported nested
> use cases. I think you mean VMCI on VMCI, right?
Right, only VMCI on VMCI.
I’ll respond to Stefano’s email for the rest of the discussion.
Thanks,
Jorgen
Powered by blists - more mailing lists