All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ligesh <xen@lxlabs.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: muli@il.ibm.com, xen-devel@lists.xensource.com,
	Michael LeMay <mdlemay@epoch.ncsc.mil>
Subject: Re: Communicating with the domU from dom0 without Network
Date: Tue, 8 Aug 2006 23:45:36 +0530	[thread overview]
Message-ID: <20060808181536.GA9793@lxlabs.com> (raw)
In-Reply-To: <C0FE64C8.A3E%Keir.Fraser@cl.cam.ac.uk>

On Tue, Aug 08, 2006 at 03:56:56PM +0100, Keir Fraser wrote:
> 
> That's not how TCP/IP works and a statement like 'serial ports do not allow
> multiple simultaneous streams' is not true since a serial port is part of a
> physical link layer so you can implement whatever protocol you like over the
> top (just as you can with e.g. an Ethernet port).
> 

 You have to build a network stack over serial port where every packet has a header with the destination port.  You can simulate the entire tcp/ip stack over the serial port, but this is again a non-trivial effort. What I meant was out-of-box, as in, you just do an open("/dev/ttyS0", "r"), and read and write, you won't get multiple connections; you will have to ensure the co-operation of the kernel, where it will have to create virtual network ports that will allow simultaneous connections to exist.

 Anyway, ultimately my proposal is that multi-stream message passing system that is not depended on the ip address would be highly desirable. You can actually implement it over the serial port or even the virtual network card itself--by using the mac addresses to identify the machines. This would make writing system management softwares much easier. Since the future seems to point at virtualization getting ubiquitous, this almost becomes a necessary feature.

--
:: Ligesh :: http://ligesh.com 

  reply	other threads:[~2006-08-08 18:15 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 [this message]
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
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=20060808181536.GA9793@lxlabs.com \
    --to=xen@lxlabs.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=mdlemay@epoch.ncsc.mil \
    --cc=muli@il.ibm.com \
    --cc=xen-devel@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.