From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <41E9F551.3060506@yahoo.com.au> Date: Sun, 16 Jan 2005 16:02:09 +1100 From: Nick Piggin MIME-Version: 1.0 Subject: Re: Odd kswapd behaviour after suspending in 2.6.11-rc1 References: <20050113085626.GA5374@blackham.com.au> <20050113101426.GA4883@blackham.com.au> <41E8ED89.8090306@yahoo.com.au> <1105785254.13918.4.camel@desktop.cunninghams> <41E8F313.4030102@yahoo.com.au> <1105786115.13918.9.camel@desktop.cunninghams> <41E8F7F7.1010908@yahoo.com.au> <20050115124018.GA24653@blackham.com.au> <20050115125311.GA19055@blackham.com.au> <41E9E5B6.1020306@yahoo.com.au> <20050116043639.GE24653@blackham.com.au> <1105851404.21576.4.camel@laptop.cunninghams> In-Reply-To: <1105851404.21576.4.camel@laptop.cunninghams> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: ncunningham@linuxmail.org Cc: Bernard Blackham , Linux Memory Management List-ID: Nigel Cunningham wrote: > Hi. > > On Sun, 2005-01-16 at 15:36, Bernard Blackham wrote: > >>On Sun, Jan 16, 2005 at 02:55:34PM +1100, Nick Piggin wrote: >> >>>Someone asked for an order 10 allocation by the looks. >>> >>>This might tell us what happened. >> >>Yep. Attached. Appears Software Suspend is asking for it as part of >>it's memory grab. Perhaps wakeup_kswapd just needs to be disabled >>while suspending? Nigel? > > > That makes sense. Okay: Nick, does it look like an issue that affects > swsusp (in kernel version) as well? If not, we can stop bugging you, and > I'll add an appropriate test to stop it acting on the basis of our > grabbing of memory while suspending. (FYI, we seek to grab all available > memory while preparing the image so that we can get some stability in > the numbers and (if we really do need to eat some memory), make headway > while leaving other processes thawed. (ie we use the vm pressure to get > memory freed until we meet our constraints). > Not sure if swsusp1 has the same issue or not. But you can probably get around the problem by setting kswapd_max_order back to zero after resuming the kswapd thread, I think? -- 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: aart@kvack.org