From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 28567986569 for ; Wed, 19 Oct 2022 03:57:09 +0000 (UTC) MIME-Version: 1.0 References: <20221017074724.89569-1-xuanzhuo@linux.alibaba.com> <1666146893.4959266-1-xuanzhuo@linux.alibaba.com> In-Reply-To: <1666146893.4959266-1-xuanzhuo@linux.alibaba.com> From: Jason Wang Date: Wed, 19 Oct 2022 11:56:52 +0800 Message-ID: Subject: Re: [virtio-dev] [PATCH 0/2] introduce virtio-ism: internal shared memory device Content-Type: text/plain; charset="UTF-8" To: Xuan Zhuo Cc: virtio-dev@lists.oasis-open.org, hans@linux.alibaba.com, herongguang@linux.alibaba.com, zmlcc@linux.alibaba.com, dust.li@linux.alibaba.com, tonylu@linux.alibaba.com, zhenzao@linux.alibaba.com, helinguo@linux.alibaba.com, gerry@linux.alibaba.com, mst@redhat.com, cohuck@redhat.com, Stefan Hajnoczi List-ID: On Wed, Oct 19, 2022 at 10:42 AM Xuan Zhuo wrote: > > On Mon, 17 Oct 2022 16:17:31 +0800, Jason Wang wrote: > > > Hi Jason, > > I think there may be some problems with the direction we are discussing. Probably not. As far as we are focusing on technology, there's nothing wrong from my perspective. And this is how the community works. Your idea needs to be justified and people are free to raise any technical questions especially considering you've posted a spec change with prototype codes but not only the idea. > Our > goal is to add an new ism device. As far as the spec is concerned, we are not > concerned with the implementation of the backend. > > The direction we should discuss is what is the difference between the ism device > and other devices such as virtio-net, and whether it is necessary to introduce > this new device. This is somehow what I want to ask, actually it's not a comparison with virtio-net but: - virtio-roce - virtio-vhost-user - virtio-(p)mem or whether we can simply add features to those devices to achieve what you want to do here. > How to share the backend with other deivce is another problem. Yes, anything that is used for your virito-ism prototype can be used for other devices. > > Our goal is to dynamically obtain a piece of memory to share with other vms. So at this level, I don't see the exact difference compared to virtio-vhost-user. Let's just focus on the API that carries on the semantic: - map/unmap - permission update The only missing piece is the per region notification. > > In a connection, this memory will be used repeatedly. As far as SMC is concerned, > it will use it as a ring. Of course, we also need a notify mechanism. > > That's what we're aiming for, so we should first discuss whether this > requirement is reasonable. So unless somebody said "no", it is fine until now. > I think it's a feature currently not supported by > other devices specified by the current virtio spce. Probably, but we've already had rfcs for roce and vhost-user. Thanks > > Thanks. > > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org