All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ligesh <xen@lxlabs.com>
To: Michael LeMay <mdlemay@epoch.ncsc.mil>
Cc: muli@il.ibm.com, xen-devel@lists.xensource.com
Subject: Re: Communicating with the domU from dom0 without Network
Date: Tue, 8 Aug 2006 20:15:45 +0530	[thread overview]
Message-ID: <20060808144545.GA6025@lxlabs.com> (raw)
In-Reply-To: <1155039451.12678.28.camel@moss-tarheels.epoch.ncsc.mil>

On Tue, Aug 08, 2006 at 08:17:31AM -0400, Michael LeMay wrote:
> >  Anyway, I am just curious. Won't an extra serial port actually solve
> > all the problems that you are intending to solve using tcp like
> > communication? Is there any limitation to serial port communication,
> > especially since everything is happening in software?
> > 

 Actually I think serial port won't be sufficient actually. I am looking at it from purely manageability perspective, but even then, serial ports does not allow multiple simultaneious streams. I think in tcp/ip, the server gets a connection at a particular master port, say 80, and then it creates a slave socket at another port and spawns a child, and child actually carries out the communication through this slave port. I am not really an expert in networking, and that's my generic idea of how networking happens. Will such a system be possible with serial ports. I don't think so. I think I will I have to come up with some protocol to make multiple streams through serial port possible. Anyway, a generalized tcp-like communication stream independent of the networking stack looks like a good idea to me.

 Or maybe you can build a networking stack kind of thing on top of the serial port. I am very new to Xen, and I will have to first get a proper system running on it test it further.

 Thanks for your comments.

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

  reply	other threads:[~2006-08-08 14:45 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 [this message]
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
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=20060808144545.GA6025@lxlabs.com \
    --to=xen@lxlabs.com \
    --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.