WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: 2005年1月21日 13:59:41 -0600
Delivery-date: 2005年1月21日 19:40:54 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0501211016500.4841@xxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: IBM
References: <1106322956.17263.26.camel@localhost > <eacc82a4050121083937725a83@xxxxxxxxxxxxxx> <Pine.LNX.4.58.0501211016500.4841@xxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On Fri, 2005年01月21日 at 11:19, Ronald G. Minnich wrote:
> On 2005年1月21日, 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@xxxxxxxxxx
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon , Anthony Liguori
Next by Date: RE: [Xen-devel] [PATCH] (revised slightly) create kernel symlinksin /boot , Ian Pratt
Previous by Thread: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon , Ronald G. Minnich
Next by Thread: Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon , Ronald G. Minnich
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /