From: Gleb Natapov <gleb@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Andrew Biggadike <biggadike@vmware.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization <virtualization@lists.linux-foundation.org>,
Zach Amsden <zach@vmware.com>, Anupam Chanda <anupamc@vmware.com>
Subject: Re: [PATCH][RFC] vmchannel a data channel between host and guest.
Date: Thu, 16 Oct 2008 10:54:49 +0200 [thread overview]
Message-ID: <20081016085449.GU11435@redhat.com> (raw)
In-Reply-To: <48F61292.9020504@codemonkey.ws>
On Wed, Oct 15, 2008 at 10:56:02AM -0500, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> Andrew,
>>
>> On Wed, Oct 15, 2008 at 07:18:52AM -0700, Andrew Biggadike wrote:
>>
>>> Gleb Natapov <gleb@redhat.com> wrote:
>>>
>>>>> Of course, you should also take a look at VMware's VMCI. If we're going
>>>>> to have a socket interface, if we can have a compatible userspace
>>>>> interface, that would probably be a good thing.
>>>>>
>>>> I looked at what I could find about VMCI (http://pubs.vmware.com/vmci-sdk/index.html).
>>>>
>>> I believe Anthony intended for you to look at the sockets interface to
>>> VMCI: http://www.vmware.com/pdf/ws65_s2_vmci_sockets.pdf.
>>>
>>>
>> Using VMCI socket requires loading kernel module in a guest and in a host.
>> Is this correct?
>>
>
> Note that their addressing scheme uses a CID/port pair. I think it's
> interesting and somewhat safe because it basically mirrors an IP/port
> pair. That makes it relatively safe because that addressing mechanism
> is well known (with it's advantages and flaws). For instance, you need
> some sort of authority to assign out ports. It doesn't really help with
> discovery either.
>
I fails to see how this is more safe that what I propose. Same problem
exactly: which ID/port to use for my service? But I also don't want to
compare proposed vmchannel and VMCI socket. They try to solve different
problems as far as I can see. VMCI tries to address intra host communication
performance problem (what about migration of a guest using it BTW? Or
security? Firewalls know nothing about it). vmchannel goal is to provide
management tools a way to communicate with in guest agents.
--
Gleb.
next prev parent reply other threads:[~2008-10-16 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 12:45 [PATCH][RFC] vmchannel a data channel between host and guest Gleb Natapov
2008-10-13 18:32 ` Anthony Liguori
2008-10-14 9:05 ` Gleb Natapov
2008-10-14 13:50 ` Anthony Liguori
2008-10-14 17:59 ` Gleb Natapov
2008-10-14 18:16 ` Anthony Liguori
2008-10-15 12:58 ` Gleb Natapov
2008-10-15 14:02 ` Anthony Liguori
2008-10-15 14:02 ` Anthony Liguori
2008-10-16 8:41 ` Gleb Natapov
2008-10-15 14:18 ` Andrew Biggadike
2008-10-15 14:30 ` Gleb Natapov
2008-10-15 14:30 ` Gleb Natapov
2008-10-15 15:00 ` Andrew Biggadike
2008-10-15 15:42 ` Gleb Natapov
2008-10-15 15:56 ` Anthony Liguori
2008-10-16 8:54 ` Gleb Natapov [this message]
2008-10-15 15:56 ` Anthony Liguori
2008-10-15 16:59 ` Andrew Biggadike
2008-10-15 16:59 ` Andrew Biggadike
2008-10-15 14:18 ` Andrew Biggadike
2008-10-15 12:58 ` Gleb Natapov
2008-10-14 18:16 ` Anthony Liguori
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=20081016085449.GU11435@redhat.com \
--to=gleb@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=anupamc@vmware.com \
--cc=biggadike@vmware.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
--cc=zach@vmware.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.