Re: Odd kswapd behaviour after suspending in 2.6.11-rc1

Nigel Cunningham
2005-01-15T10:34:14Z

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