From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Daniel Stodden <stodden@cs.tum.edu>
Cc: xen@lxlabs.com, muli@il.ibm.com, xen-devel@lists.xensource.com,
Michael LeMay <mdlemay@epoch.ncsc.mil>
Subject: Re: Re: Communicating with the domU from dom0 without Network
Date: Wed, 09 Aug 2006 00:04:07 +0100 [thread overview]
Message-ID: <1155078247.10328.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1155070472.5293.97.camel@lapbode42.lrr.in.tum.de>
On Tue, 2006-08-08 at 22:54 +0200, Daniel Stodden wrote:
> make it absolutely clear to users, that if they wish to configure fast
> host-local inter-domain-communications, they get what they desire: fast,
> but host-local domain-interdependent communications. if your customer
> asks for light-weight optimized inter-domain-communication, ask her if
> that specific application would not rather demand for regular
> inter-process-communications on a standard operating system, because
> that's what they get then.
The xenidc code that I wrote was an efficient interdomain transport
which was compatible with a network transparent implementation.
Harry.
next prev parent reply other threads:[~2006-08-08 23:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 12:40 Communicating with the domU from dom0 without Network Ligesh
2006-08-07 12:57 ` Muli Ben-Yehuda
2006-08-07 13:31 ` Ligesh
2006-08-07 13:32 ` Muli Ben-Yehuda
2006-08-07 13:49 ` Ligesh
2006-08-07 16:18 ` Michael LeMay
2006-08-08 10:49 ` Ligesh
2006-08-08 12:17 ` Michael LeMay
2006-08-08 14:45 ` Ligesh
2006-08-08 14:56 ` Keir Fraser
2006-08-08 18:15 ` Ligesh
2006-08-08 18:59 ` Ian Campbell
2006-08-08 14:41 ` Mike D. Day
2006-08-08 20:54 ` Daniel Stodden
2006-08-08 23:04 ` Harry Butterworth [this message]
2006-08-08 23:34 ` Daniel Stodden
2006-08-08 23:47 ` Ligesh
2006-08-09 12:09 ` Daniel Stodden
2006-08-09 12:22 ` Daniel Stodden
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=1155078247.10328.1.camel@localhost.localdomain \
--to=harry@hebutterworth.freeserve.co.uk \
--cc=mdlemay@epoch.ncsc.mil \
--cc=muli@il.ibm.com \
--cc=stodden@cs.tum.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen@lxlabs.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.