From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1142889937.441f1dd19e90f@vds.kolivas.org> Date: Tue, 21 Mar 2006 08:25:37 +1100 From: kernel@kolivas.org Subject: Re: [PATCH][3/3] mm: swsusp post resume aggressive swap prefetch References: <200603200234.01472.kernel@kolivas.org> <200603202247.38576.rjw@sisk.pl> In-Reply-To: <200603202247.38576.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-linux-mm@kvack.org Return-Path: To: "Rafael J. Wysocki" Cc: linux list , ck list , Andrew Morton , Pavel Machek , linux-mm@kvack.org List-ID: Quoting "Rafael J. Wysocki" : > Hi, > > On Sunday 19 March 2006 16:34, Con Kolivas wrote: > > > > Swsusp reclaims a lot of memory during the suspend cycle and can benefit > > from the aggressive_swap_prefetch mode immediately upon resuming. > > It slows down the resume on my box way too much. Last time it took 10x more > time than actually reading the image. > > I think the problem is for the userland suspend (which I use) it's done too > early, > when the image pages are still in the swap, so they are taken into > consideration > by the aggressive prefetch. If that really is the case, the solution would > be to > trigger the aggressive prefetch from the userland, if needed, after the > image > pages have been released. I assume this is unique to the userland resume as the in-kernel resume is not slowed down? If so, is there a way to differentiate the two so we only aggressively prefetch on kernel resume - is that what you meant by doing it in the other file? Cheers, Con -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org