From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
MAYAP christine <christine.mayapkamga@enseeiht.fr>
Subject: Re: Fwd: Fwd: [Xen-users] Shared memory between Dom0 and DomU
Date: Wed, 16 Mar 2011 09:49:09 -0400 [thread overview]
Message-ID: <20110316134909.GC4881@dumpdata.com> (raw)
In-Reply-To: <1300262582.15812.18.camel@localhost.localdomain>
On Wed, Mar 16, 2011 at 08:03:02AM +0000, Ian Campbell wrote:
> On Wed, 2011-03-16 at 07:58 +0000, Pasi Kärkkäinen wrote:
> > On Tue, Mar 15, 2011 at 11:17:14PM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Thu, Mar 10, 2011 at 11:03:25AM +0100, MAYAP christine wrote:
> > > > Hello,
> > > >
> > > > I'm still reading document about inter-VM communication via shared memory.
> > > > I found many reference about IVC.
> > >
> > > The IVC on I think is the XCP source code. Google for XCP source code
> > > and you should find it.
> > >
> >
> > There's also V4V in Citrix XenClient.. sources available in the source iso.
> > It includes xen patches, linux kernel patches, and user space libraries providing a socket-like API (for linux and windows).
>
> I wasn't aware of an IVC mechanisms in XCP so I suspect this is what
> Konrad was thinking of.
That was it. V4V.. sounds similar enough to IVC. Three letter acronym.
prev parent reply other threads:[~2011-03-16 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 10:03 Fwd: Fwd: [Xen-users] Shared memory between Dom0 and DomU MAYAP christine
2011-03-16 3:17 ` Konrad Rzeszutek Wilk
2011-03-16 7:58 ` Pasi Kärkkäinen
2011-03-16 8:03 ` Ian Campbell
2011-03-16 13:49 ` Konrad Rzeszutek Wilk [this message]
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=20110316134909.GC4881@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=christine.mayapkamga@enseeiht.fr \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.