Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 7 Mar 2003 06:01:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 7 Mar 2003 06:00:56 -0500 Received: from [195.39.17.254] ([195.39.17.254]:5892 "EHLO Elf.ucw.cz") by vger.kernel.org with ESMTP id ; Fri, 7 Mar 2003 06:00:26 -0500 Date: Wed, 5 Mar 2003 19:02:22 +0100 From: Pavel Machek To: Patrick Mochel Cc: Nigel Cunningham , Pavel Machek , Linux Kernel Mailing List Subject: Re: SWSUSP Discontiguous pagedir patch Message-ID: <20030305180222.GA2781@zaurus.ucw.cz> References: <1046487717.4616.22.camel@laptop-linux.cunninghams> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1235 Lines: 37 Hi! > > Thus, I still think we can go with the patch I submitted before. I've > > rediffed it against 2.5.63 (less the bits already applied). > > I've spent the last week reading, reviewing, and rewriting major portions > of swsusp. I've actually been reasonably impressed, once I was able to get > the code into a much more readable state. > > All in all, I think the idea of saving state to swap is dangerous for > various reasons. However, I like some of the other concepts of the code, Can you elaborate? I believe writing to swap is good for user; and it works. > and will use them in developing a more palatable mechanism of doing STDs What is STD? > http://ldm.bkbits.net:8080/linux-2.5-power > Can you post cumulative diff of work-in-progress? I am not permitted to use bk. Also please make sure that you post the diff before you merge it (and please Cc me). Pavel -- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need... - 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/