All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: [PATCH] xenctld - a control channel multiplexing daemon
Date: Fri, 21 Jan 2005 13:59:41 -0600	[thread overview]
Message-ID: <1106337581.18070.13.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0501211016500.4841@linux.site>

On Fri, 2005-01-21 at 11:19, Ronald G. Minnich wrote:
> On Fri, 21 Jan 2005, Andrew Warfield wrote:
> 
> > > 1) Change xcs to use unix domain sockets.
> > 
> > The original thought behind using ip sockets behind xcs was in
> > planning for cluster management.  Obviously there are other ways to
> > map this in, I'm not terribly fussy on this point.
> 
> how will this work if we run a 256-node xen cluster (which we will be
> doing here for testing)? Wouldn't we want the IP socket?

It's not so much about whether there would be an IP interface at all,
more about what's the lowest possible interface.  A daemon that uses the
domain socket interface could then export an IP interface.

Just running a single Xen server though, you probably don't want a port
open if it doesn't have to be.

Regards,
-- 
Anthony Liguori
Linux Technology Center (LTC) - IBM Austin
E-mail: aliguori@us.ibm.com
Phone: (512) 838-1208




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  reply	other threads:[~2005-01-21 19:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 15:55 [PATCH] xenctld - a control channel multiplexing daemon Anthony Liguori
2005-01-21 16:39 ` Andrew Warfield
2005-01-21 17:19   ` Ronald G. Minnich
2005-01-21 19:59     ` Anthony Liguori [this message]
2005-01-21 20:44       ` Ronald G. Minnich
2005-01-21 21:14         ` Anthony Liguori
2005-01-21 20:54           ` Ronald G. Minnich
2005-01-21 21:28             ` Anthony Liguori
2005-01-21 21:37             ` Jared Rhine
2005-01-24 15:33               ` Ronald G. Minnich
2005-01-24 16:35                 ` Anthony Liguori
2005-01-24 16:55                   ` Jared Rhine
     [not found]                     ` <Pine.LNX.4.58.0501240957520.12186@bluesteel.lanl.gov>
2005-01-24 17:52                       ` Jared Rhine
2005-01-24 19:11                         ` Anthony Liguori
2005-01-24 19:07                     ` Anthony Liguori
2005-01-24 20:44                       ` B.G. Bruce
2005-01-26  2:31                       ` Jacob Gorm Hansen
2005-01-26  5:43                         ` Anthony Liguori
2005-01-26  6:59                           ` Jacob Gorm Hansen
2005-01-21 19:56   ` Anthony Liguori
2005-01-26  0:21   ` Michael Hohnbaum
2005-01-26 14:33     ` Andrew Warfield
2005-01-26 19:31       ` Anthony Liguori
2005-01-26 19:11         ` Andrew Warfield
2005-01-26 20:01           ` Anthony Liguori
2005-01-26 21:21             ` Daniel Stekloff
2005-01-26 22:28               ` Anthony Liguori
2005-01-26 21:57                 ` Daniel Stekloff
2005-01-26 21:49             ` Michael Hohnbaum
2005-01-26 22:57               ` Anthony Liguori
2005-01-26 23:55                 ` Michael Hohnbaum
2005-01-26 23:59                 ` Daniel Stekloff
2005-01-27  7:05                   ` Tobias Hunger
2005-01-27 14:19                   ` Anthony Liguori
2005-01-27 18:05                     ` Daniel Stekloff
2005-01-28  9:17                       ` Steven Hand
2005-01-28 16:56                         ` Daniel Stekloff
2005-01-27  0:13                 ` Daniel Stekloff
2005-01-27  3:48                 ` Daniel Stekloff
2005-01-26 23:36       ` Daniel Stekloff

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=1106337581.18070.13.camel@localhost \
    --to=aliguori@us.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.