[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a47ecb89-b677-2001-5573-d71be5edd4c9@redhat.com>
Date: Fri, 25 Dec 2020 14:59:21 +0800
From: Jason Wang <jasowang@...hat.com>
To: Yongji Xie <xieyongji@...edance.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>, sgarzare@...hat.com,
Parav Pandit <parav@...dia.com>, akpm@...ux-foundation.org,
Randy Dunlap <rdunlap@...radead.org>,
Matthew Wilcox <willy@...radead.org>, viro@...iv.linux.org.uk,
axboe@...nel.dk, bcrl@...ck.org, corbet@....net,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
kvm@...r.kernel.org, linux-aio@...ck.org,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC v2 06/13] vduse: Introduce VDUSE - vDPA Device in Userspace
On 2020/12/24 下午4:34, Yongji Xie wrote:
>> Yes, the disadvantage is the performance. But it should be simpler (I
>> guess) and we know it can succeed.
>>
> Yes, another advantage is that we can support the VM using anonymous memory.
Exactly.
>
>>> I think I can try this in v3. And the
>>> MMU-based IOMMU implementation can be a future optimization in the
>>> virtio-vdpa case. What's your opinion?
>> Maybe I was wrong, but I think we can try as what has been proposed here
>> first and use shadow virtqueue as backup plan if we fail.
>>
> OK, I will continue to work on this proposal.
Thanks
>
Powered by blists - more mailing lists