Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261151AbTEERZE (ORCPT ); Mon, 5 May 2003 13:25:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261158AbTEERZE (ORCPT ); Mon, 5 May 2003 13:25:04 -0400 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:6467 "EHLO frodo.biederman.org") by vger.kernel.org with ESMTP id S261151AbTEERZD (ORCPT ); Mon, 5 May 2003 13:25:03 -0400 To: Steven Cole Cc: linux-kernel@vger.kernel.org, Larry McVoy , Linus Torvalds Subject: Re: Kernel hot-swap using Kexec, BProc and CC/SMP Clusters. References: <1052140733.2163.93.camel@spc9.esa.lanl.gov> From: ebiederm@xmission.com (Eric W. Biederman) Date: 05 May 2003 11:34:24 -0600 In-Reply-To: <1052140733.2163.93.camel@spc9.esa.lanl.gov> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 968 Lines: 20 So summarize: 1) Run multiple kernels (minimally kernels A and B) 2) Migrate processes from kernel A to kernel B 3) Use kexec to replace kernel A once all processes have left. 4) Repeat for all other kernels. On two simple machines working in tandem (The most common variation used for high availability this should be easy to do). And it is preferable to a reboot because of the additional control and speed. Thank you for the perspective. This looks like I line I can sell to get some official time to work on kexec and it's friends more actively. >From what I have seen process migration/process check-pointing is currently the very rough area. The interesting thing becomes how do you measure system uptime. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/