From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: RFC: virtio-peer shared memory based peer communication device Date: Mon, 21 Sep 2015 12:47:26 +0200 Message-ID: <55FFE03E.6080106@siemens.com> References: <20150831160655-mutt-send-email-mst@redhat.com> <55ED854A.1080804@huawei.com> <55EFF03A.4000109@huawei.com> <55FC3BE7.5010503@huawei.com> <55FC7DFA.80204@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55FC7DFA.80204@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Paolo Bonzini , Claudio Fontana , "Zhang, Yang Z" , "Michael S. Tsirkin" , "qemu-devel@nongnu.org" , "virtualization@lists.linux-foundation.org" , "virtio-dev@lists.oasis-open.org" , "opnfv-tech-discuss@lists.opnfv.org" List-Id: virtualization@lists.linuxfoundation.org On 2015-09-18 23:11, Paolo Bonzini wrote: > On 18/09/2015 18:29, Claudio Fontana wrote: >> >> this is a first RFC for virtio-peer 0.1, which is still very much a work in progress: >> >> https://github.com/hw-claudio/virtio-peer/wiki >> >> It is also available as PDF there, but the text is reproduced here for commenting: >> >> Peer shared memory communication device (virtio-peer) > > Apart from the windows idea, how does virtio-peer compare to virtio-rpmsg? rpmsg is a very specialized thing. It targets single AMP cores, assuming that those have full access to the main memory. And it is also a centralized approach where all message go through the main Linux instance. I suspect we could cover that use case as well with generic inter-vm shared memory device, but I didn't think about all details yet. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdydY-0007p7-Dn for qemu-devel@nongnu.org; Mon, 21 Sep 2015 06:47:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZdydU-00035c-45 for qemu-devel@nongnu.org; Mon, 21 Sep 2015 06:47:56 -0400 Received: from thoth.sbs.de ([192.35.17.2]:36765) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZdydT-00031x-RB for qemu-devel@nongnu.org; Mon, 21 Sep 2015 06:47:52 -0400 References: <20150831160655-mutt-send-email-mst@redhat.com> <55ED854A.1080804@huawei.com> <55EFF03A.4000109@huawei.com> <55FC3BE7.5010503@huawei.com> <55FC7DFA.80204@redhat.com> From: Jan Kiszka Message-ID: <55FFE03E.6080106@siemens.com> Date: Mon, 21 Sep 2015 12:47:26 +0200 MIME-Version: 1.0 In-Reply-To: <55FC7DFA.80204@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] RFC: virtio-peer shared memory based peer communication device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , Claudio Fontana , "Zhang, Yang Z" , "Michael S. Tsirkin" , "qemu-devel@nongnu.org" , "virtualization@lists.linux-foundation.org" , "virtio-dev@lists.oasis-open.org" , "opnfv-tech-discuss@lists.opnfv.org" On 2015-09-18 23:11, Paolo Bonzini wrote: > On 18/09/2015 18:29, Claudio Fontana wrote: >> >> this is a first RFC for virtio-peer 0.1, which is still very much a work in progress: >> >> https://github.com/hw-claudio/virtio-peer/wiki >> >> It is also available as PDF there, but the text is reproduced here for commenting: >> >> Peer shared memory communication device (virtio-peer) > > Apart from the windows idea, how does virtio-peer compare to virtio-rpmsg? rpmsg is a very specialized thing. It targets single AMP cores, assuming that those have full access to the main memory. And it is also a centralized approach where all message go through the main Linux instance. I suspect we could cover that use case as well with generic inter-vm shared memory device, but I didn't think about all details yet. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux