From: Henning Schild <henning.schild@siemens.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Vincent JARDIN <vincent.jardin@6wind.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Using virtio for inter-VM communication
Date: Thu, 12 Jun 2014 09:44:13 +0200 [thread overview]
Message-ID: <20140612094413.15e56938@nbschild1> (raw)
In-Reply-To: <87ppie1v4r.fsf@blackfin.pond.sub.org>
On Thu, 12 Jun 2014 08:48:04 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> Vincent JARDIN <vincent.jardin@6wind.com> writes:
>
> > On 10/06/2014 18:48, Henning Schild wrote:> Hi,
> >> In a first prototype i implemented a ivshmem[2] device for the
> >> hypervisor. That way we can share memory between virtual machines.
> >> Ivshmem is nice and simple but does not seem to be used anymore.
> >> And it
> >> does not define higher level devices, like a console.
> >
> > FYI, ivhsmem is used here:
> > http://dpdk.org/browse/memnic/tree/
> >
> > http://dpdk.org/browse/memnic/tree/pmd/pmd_memnic.c#n449
> >
> > There are some few other references too, if needed.
>
> It may be used, but that doesn't mean it's maintained, or robust
> against abuse. My advice is to steer clear of it.
Could you elaborate on why you advice against it?
Henning
next prev parent reply other threads:[~2014-06-12 7:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 16:48 [Qemu-devel] Using virtio for inter-VM communication Henning Schild
2014-06-10 22:15 ` Vincent JARDIN
2014-06-12 6:48 ` Markus Armbruster
2014-06-12 7:44 ` Henning Schild [this message]
2014-06-12 9:31 ` Vincent JARDIN
2014-06-12 12:55 ` Markus Armbruster
2014-06-12 14:40 ` [Qemu-devel] Why I advise against using ivshmem (was: Using virtio for inter-VM communication) Markus Armbruster
2014-06-12 16:02 ` [Qemu-devel] Why I advise against using ivshmem Vincent JARDIN
2014-06-12 16:54 ` Paolo Bonzini
2014-06-13 8:46 ` Markus Armbruster
2014-06-13 9:26 ` Vincent JARDIN
2014-06-13 9:31 ` Jobin Raju George
2014-06-13 9:48 ` Olivier MATZ
2014-06-13 10:09 ` Paolo Bonzini
2014-06-13 13:41 ` Vincent JARDIN
2014-06-13 14:10 ` Paolo Bonzini
2014-06-14 18:01 ` Vincent JARDIN
2014-06-17 2:54 ` Stefan Hajnoczi
2014-06-17 9:03 ` David Marchand
2014-06-17 9:44 ` Paolo Bonzini
2014-06-18 10:48 ` Stefan Hajnoczi
2014-06-18 14:57 ` David Marchand
2014-06-18 15:10 ` Paolo Bonzini
2014-06-21 9:34 ` Stefan Hajnoczi
2014-06-26 20:02 ` Cam Macdonell
2014-06-18 15:01 ` Andreas Färber
2014-06-19 8:25 ` David Marchand
2014-06-30 11:10 ` Markus Armbruster
2014-06-18 10:51 ` Stefan Hajnoczi
2014-06-18 14:58 ` David Marchand
2014-06-18 14:22 ` Claudio Fontana
2014-06-13 9:29 ` Jobin Raju George
2014-06-12 2:27 ` [Qemu-devel] Using virtio for inter-VM communication Rusty Russell
2014-06-12 5:32 ` Jan Kiszka
2014-06-13 0:47 ` Rusty Russell
2014-06-13 6:23 ` Jan Kiszka
2014-06-13 8:45 ` Paolo Bonzini
2014-06-15 6:20 ` Jan Kiszka
2014-06-17 5:24 ` Paolo Bonzini
2014-06-17 5:57 ` Jan Kiszka
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=20140612094413.15e56938@nbschild1 \
--to=henning.schild@siemens.com \
--cc=armbru@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=vincent.jardin@6wind.com \
--cc=virtualization@lists.linux-foundation.org \
/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).