Re: Odd kswapd behaviour after suspending in 2.6.11-rc1

Nick Piggin
2005-01-16T05:02:09Z

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?