From owner-freebsd-cluster Wed Mar 6 10: 8:16 2002 Delivered-To: freebsd-cluster@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with SMTP id EBEC237B423 for ; Wed, 6 Mar 2002 10:07:52 -0800 (PST) Received: (qmail 234116 invoked from network); 6 Mar 2002 11:07:51 -0700 Received: from snaresland.acl.lanl.gov (128.165.147.113) by acl.lanl.gov with SMTP; 6 Mar 2002 11:07:51 -0700 Received: (qmail 9936 invoked by uid 3499); 6 Mar 2002 11:07:51 -0700 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Mar 2002 11:07:51 -0700 Date: Wed, 6 Mar 2002 11:07:51 -0700 (MST) From: Ronald G Minnich X-X-Sender: To: Andy Sporner Cc: , Jason Fried Subject: RE: FreeBSD Cluster at SLU In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-cluster@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 6 Mar 2002, Andy Sporner wrote: > > The idea is that whereever a process is started, it makes an entry in > the process table. The PID's are assigned in a N-Modulus approach so that > the PID determines the home node of the process. When a process migrates, > it keeps it's entry on the home node and a new entry is created on the > new host node. If it should move again, the home node is updated. I haven't > started implementing or benchmarking this yet, so it could change, but that > is the initial idea. this is very similar to bproc. Would a single hot-spare approach do the job? I do know there is a telecom company using bproc to do this type of thing. > Since the model is for making a scalable networking application platform, > all of the aspects of the process move with the process (including sockets). movable sockets sure would be nice. your work sounds neat. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message