Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964783AbVLIPsY (ORCPT ); Fri, 9 Dec 2005 10:48:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964792AbVLIPsY (ORCPT ); Fri, 9 Dec 2005 10:48:24 -0500 Received: from cantor2.suse.de ([195.135.220.15]:17878 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S964783AbVLIPsX (ORCPT ); Fri, 9 Dec 2005 10:48:23 -0500 Message-ID: <4399A737.40809@suse.de> Date: Fri, 09 Dec 2005 16:48:07 +0100 From: Stefan Seyfried User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050715 Thunderbird/1.0.6 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Rafael J. Wysocki" Cc: Pavel Machek , LKML , Andrew Morton Subject: Re: [PATCH][mm] swsusp: limit image size References: <200512072246.06222.rjw@sisk.pl> In-Reply-To: <200512072246.06222.rjw@sisk.pl> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 988 Lines: 22 Rafael J. Wysocki wrote: > The following patch limits the size of the suspend image to approx. 500 MB, > which should improve the overall performance of swsusp on systems with > more than 1 GB of RAM. > > It introduces the constant IMAGE_SIZE that can be set to the preferred size > of the image (in MB) and modifies the memory-shrinking part of > swsusp to take this constant into account (500 is the default value > of IMAGE_SIZE). What happens if IMAGE_SIZE is bigger than free swap? Do we "try harder" or do we fail? -- Stefan Seyfried \ "I didn't want to write for pay. I QA / R&D Team Mobile Devices \ wanted to be paid for what I write." SUSE LINUX Products GmbH, N?rnberg \ -- Leonard Cohen - 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/