From: Paolo Bonzini <pbonzini@redhat.com>
To: 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>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] RFC: virtio-peer shared memory based peer communication device
Date: Fri, 18 Sep 2015 23:11:22 +0200 [thread overview]
Message-ID: <55FC7DFA.80204@redhat.com> (raw)
In-Reply-To: <55FC3BE7.5010503@huawei.com>
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?
Paolo
next prev parent reply other threads:[~2015-09-18 21:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 14:11 [Qemu-devel] rfc: vhost user enhancements for vm2vm communication Michael S. Tsirkin
2015-08-31 18:35 ` Nakajima, Jun
2015-09-01 3:03 ` Varun Sethi
2015-09-01 8:30 ` Michael S. Tsirkin
2015-09-01 8:17 ` Michael S. Tsirkin
2015-09-01 22:56 ` Nakajima, Jun
2015-10-06 21:42 ` Nakajima, Jun
2015-10-07 5:39 ` Michael S. Tsirkin
2015-09-01 7:35 ` Jan Kiszka
2015-09-01 8:01 ` Michael S. Tsirkin
2015-09-01 9:11 ` Jan Kiszka
2015-09-01 9:24 ` Michael S. Tsirkin
2015-09-01 14:09 ` Jan Kiszka
2015-09-01 14:34 ` Michael S. Tsirkin
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
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
2015-09-03 10:25 ` Jan Kiszka
2015-09-07 12:38 ` Claudio Fontana
2015-09-09 6:40 ` [Qemu-devel] [opnfv-tech-discuss] " Zhang, Yang Z
2015-09-09 8:39 ` Claudio Fontana
2015-09-18 16:29 ` [Qemu-devel] RFC: virtio-peer shared memory based peer communication device Claudio Fontana
2015-09-18 21:11 ` Paolo Bonzini [this message]
2015-09-21 10:47 ` Jan Kiszka
2015-09-21 12:15 ` Paolo Bonzini
2015-09-21 12:13 ` Michael S. Tsirkin
2015-09-21 12:32 ` Jan Kiszka
2015-09-24 10:04 ` Michael S. Tsirkin
2015-09-09 7:06 ` [Qemu-devel] rfc: vhost user enhancements for vm2vm communication Michael S. Tsirkin
2015-09-11 15:39 ` Claudio Fontana
2015-09-13 9:12 ` Michael S. Tsirkin
2015-09-14 0:43 ` [Qemu-devel] [opnfv-tech-discuss] " Zhang, Yang Z
2015-09-14 16:00 ` [Qemu-devel] [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=55FC7DFA.80204@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).