From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 25 02:04:10 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDF016A4CF for ; Tue, 25 Jan 2005 02:04:10 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFD0043D46 for ; Tue, 25 Jan 2005 02:04:09 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.13.1) with ESMTP id j0P23Yi1003411; Mon, 24 Jan 2005 21:03:34 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.13.1/Submit) id j0P23YuR003410; Mon, 24 Jan 2005 21:03:34 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Mon, 24 Jan 2005 21:03:34 -0500 From: David Schultz To: Bruce M Simpson Message-ID: <20050125020334.GA3266@VARK.MIT.EDU> Mail-Followup-To: Bruce M Simpson , Ryan Sommers , hackers@FreeBSD.ORG, References: <86pszu639o.fsf@borg.borderworlds.dk> <86brbe6052.fsf@borg.borderworlds.dk> <200501242240.j0OMeIXP043763@apollo.backplane.com> <41F59242.7090900@jonny.eng.br> <41F5A2DE.5000306@gamersimpact.com> <20050125014935.GD47638@dhcp120.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050125014935.GD47638@dhcp120.icir.org> cc: Ryan Sommers cc: hackers@FreeBSD.ORG cc: "=?us-ascii:iso-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?=" Subject: Re: Resuming from a crashdump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 02:04:10 -0000 On Tue, Jan 25, 2005, Bruce M Simpson wrote: > If we could take a clean subsystem-by-subsystem approach to marshaling > kernel state to disk, that would be good. What gives me particular pain > here is dealing with things like the filesystem. How does one deal with > open files, etc, with pending I/O? You just write an image of physical memory to disk, and the data structures behind the open files come back exactly as they were before. ;-) The hard part, I think, is getting all the device drivers to understand how to reinitialize the hardware in exactly the same state it was in before the suspend. BTW, contrary to what Matt said, I don't think network connections are a big deal. If you turn your computer on after a long plane flight to Tahiti, and the kernel still thinks you have active TCP connections, it will quickly discover that the remote host doesn't think so and take appropriate action. I'm pretty sure Windows doesn't do anything special with network connections, because a friend of mine says he manages to turn off his laptop, walk to the other side of a building and down a few floors, turn the laptop back on, and still be logged in to a remote server via SSH.