virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Claudio Fontana <claudio.fontana@huawei.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"opnfv-tech-discuss@lists.opnfv.org"
	<opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: RFC: virtio-peer shared memory based peer communication device
Date: Mon, 21 Sep 2015 14:15:41 +0200	[thread overview]
Message-ID: <55FFF4ED.4000908@redhat.com> (raw)
In-Reply-To: <55FFE03E.6080106@siemens.com>



On 21/09/2015 12:47, Jan Kiszka wrote:
>> > 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.

Yes, this is why I did say "apart from the windows idea".

> 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.

The virtqueue handling seems very similar between the two.  However, the
messages for rpmsg however have a small header (struct rpmsg_hdr in
include/linux/rpmsg.h) and there is a weird feature bit VIRTIO_RPMSG_F_NS.

So I guess virtio-rpmsg and virtio-peer are about as similar as
virtio-serial and virtio-peer.

Paolo

  reply	other threads:[~2015-09-21 12:15 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150831160655-mutt-send-email-mst@redhat.com>
2015-08-31 18:35 ` rfc: vhost user enhancements for vm2vm communication Nakajima, Jun
2015-09-01  3:03   ` [Qemu-devel] " Varun Sethi
2015-09-01  8:17   ` Michael S. Tsirkin
     [not found]   ` <BN1PR0301MB0627D7AE90FC7A08545848CAEA6A0@BN1PR0301MB0627.namprd03.prod.outlook.com>
2015-09-01  8:30     ` [Qemu-devel] " Michael S. Tsirkin
     [not found]   ` <20150901110627-mutt-send-email-mst@redhat.com>
2015-09-01 22:56     ` Nakajima, Jun
2015-10-06 21:42   ` Nakajima, Jun
     [not found]   ` <CAL54oT1Q=+y_oNuUGq=KOXa7Yc-skNeXzcSn4kza3EpCKUYQ1w@mail.gmail.com>
2015-10-07  5:39     ` Michael S. Tsirkin
2015-09-01  7:35 ` Jan Kiszka
2015-09-01  8:01   ` Michael S. Tsirkin
     [not found]   ` <20150901104914-mutt-send-email-mst@redhat.com>
2015-09-01  9:11     ` Jan Kiszka
2015-09-01  9:24       ` Michael S. Tsirkin
     [not found]       ` <20150901121743-mutt-send-email-mst@redhat.com>
2015-09-01 14:09         ` Jan Kiszka
2015-09-01 14:34           ` Michael S. Tsirkin
     [not found]           ` <20150901172239-mutt-send-email-mst@redhat.com>
2015-09-01 15:34             ` Jan Kiszka
2015-09-01 16:02               ` Michael S. Tsirkin
2015-09-01 16:28                 ` Jan Kiszka
2015-09-02  0:01                   ` Nakajima, Jun
2015-09-02 12:15                     ` Michael S. Tsirkin
2015-09-03  4:45                       ` Nakajima, Jun
     [not found]                       ` <CAL54oT1km9+wFBLfPzjW=sLCdfNg+yh=whFsE_f+udTHkSOs_g@mail.gmail.com>
2015-09-03  8:09                         ` Michael S. Tsirkin
2015-09-03  8:08                   ` Michael S. Tsirkin
2015-09-03  8:21                     ` Jan Kiszka
2015-09-03  8:37                       ` Michael S. Tsirkin
     [not found]                       ` <20150903112343-mutt-send-email-mst@redhat.com>
2015-09-03 10:25                         ` Jan Kiszka
2015-09-07 12:38 ` Claudio Fontana
     [not found] ` <55ED854A.1080804@huawei.com>
2015-09-09  6:40   ` [opnfv-tech-discuss] " Zhang, Yang Z
2015-09-09  7:06   ` Michael S. Tsirkin
     [not found]   ` <A9667DDFB95DB7438FA9D7D576C3D87E0AD9AB0B@SHSMSX104.ccr.corp.intel.com>
2015-09-09  8:39     ` [opnfv-tech-discuss] " Claudio Fontana
     [not found]     ` <55EFF03A.4000109@huawei.com>
2015-09-18 16:29       ` RFC: virtio-peer shared memory based peer communication device Claudio Fontana
     [not found]       ` <55FC3BE7.5010503@huawei.com>
2015-09-18 21:11         ` Paolo Bonzini
2015-09-21 10:47           ` Jan Kiszka
2015-09-21 12:15             ` Paolo Bonzini [this message]
2015-09-21 12:13         ` Michael S. Tsirkin
     [not found]         ` <20150921150953-mutt-send-email-mst@redhat.com>
2015-09-21 12:32           ` Jan Kiszka
2015-09-24 10:04             ` Michael S. Tsirkin
     [not found]   ` <20150909095258-mutt-send-email-mst@redhat.com>
2015-09-11 15:39     ` rfc: vhost user enhancements for vm2vm communication Claudio Fontana
2015-09-13  9:12       ` Michael S. Tsirkin
     [not found]       ` <20150913120821-mutt-send-email-mst@redhat.com>
2015-09-14  0:43         ` [opnfv-tech-discuss] " Zhang, Yang Z
2015-09-14 16:00 ` [virtio-dev] " 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=55FFF4ED.4000908@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=claudio.fontana@huawei.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mst@redhat.com \
    --cc=opnfv-tech-discuss@lists.opnfv.org \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yang.z.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).