Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752322AbWCPKsl (ORCPT ); Thu, 16 Mar 2006 05:48:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752337AbWCPKsl (ORCPT ); Thu, 16 Mar 2006 05:48:41 -0500 Received: from mail26.syd.optusnet.com.au ([211.29.133.167]:59628 "EHLO mail26.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S1752322AbWCPKsk (ORCPT ); Thu, 16 Mar 2006 05:48:40 -0500 From: Con Kolivas To: Pavel Machek Subject: Re: does swsusp suck after resume for you? Date: Thu, 16 Mar 2006 21:47:56 +1100 User-Agent: KMail/1.9.1 Cc: ck@vds.kolivas.org, Stefan Seyfried , Jun OKAJIMA , linux-kernel@vger.kernel.org, Andreas Mohr References: <200603101704.AA00798@bbb-jz5c7z9hn9y.digitalinfra.co.jp> <200603162133.26771.kernel@kolivas.org> <20060316104630.GA9399@atrey.karlin.mff.cuni.cz> In-Reply-To: <20060316104630.GA9399@atrey.karlin.mff.cuni.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603162147.56725.kernel@kolivas.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1631 Lines: 37 On Thursday 16 March 2006 21:46, Pavel Machek wrote: > > On Thursday 16 March 2006 04:59, Pavel Machek wrote: > > The tunable in /proc/sys/vm/swap_prefetch is now bitwise ORed: > > 1 = Normal background swap prefetching when load is light > > 2 = Aggressively swap prefetch as much as possible > > > > And once the "aggressive" bit is set it will prefetch as much as it can > > and then disable the aggressive bit. Thus if you set this value to 3 it > > will prefetch aggressively and then drop back to the default of 1. This > > makes it easy to simply set the aggressive flag once and forget about it. > > I've booted and tested this feature and it's working nicely. Where > > exactly you'd set this in your resume scripts I'm not sure. A rolled up > > patch against 2.6.16-rc6-mm1 is here for simplicity: > > http://ck.kolivas.org/patches/swap-prefetch/2.6.16-rc6-mm1-swap_prefetch_ > >suspend_test.patch > > > > and the incremental on top of the 4 patches pending for the next -mm is > > below. > > > > Comments and testers most welcome. > > Looks okay, but... what happens if I set /proc/sys/vm/swap_prefetch to > "2"? Do nothing but do it agresively? > > Maybe having 0 = off, 1 = normal, 2 = aggressive would be less error > prone for the users. 2 means aggressively prefetch as much as possible and then disable swap prefetching from that point on. Too confusing? Cheers, Con - 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/