From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: Odd kswapd behaviour after suspending in 2.6.11-rc1 From: Nigel Cunningham Reply-To: ncunningham@linuxmail.org In-Reply-To: <41E8ED89.8090306@yahoo.com.au> References: <20050113061401.GA7404@blackham.com.au> <41E61479.5040704@yahoo.com.au> <20050113085626.GA5374@blackham.com.au> <20050113101426.GA4883@blackham.com.au> <41E8ED89.8090306@yahoo.com.au> Content-Type: text/plain Message-Id: <1105785254.13918.4.camel@desktop.cunninghams> Mime-Version: 1.0 Date: Sat, 15 Jan 2005 21:34:14 +1100 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Nick Piggin Cc: Bernard Blackham , Linux Memory Management List-ID: Hi Nick and Bernard. On Sat, 2005-01-15 at 21:16, Nick Piggin wrote: > OK I think the problem is due to swsusp allocating a very large > chunk of memory before suspending. After resuming, kswapd is more > or less in the same state and tries a bit too hard to free things. I'm not sure about this theory. The normal case will be that all allocations (maybe one or two order 1 or order 2 allocations if I've forgotten something) are order 0 and processes are thawed after we've freed all the memory we were using. Could that still trigger kswapd? > Thanks for the report... I'll come up with something for you to try > in the next day or so. I'm flying to America on Monday, but I'll try to keep up with the progress in this and do anything I can to help. Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574 -- 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