linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: ncunningham@linuxmail.org
Cc: Bernard Blackham <bernard@blackham.com.au>,
	Linux Memory Management <linux-mm@kvack.org>
Subject: Re: Odd kswapd behaviour after suspending in 2.6.11-rc1
Date: Sun, 16 Jan 2005 16:02:09 +1100	[thread overview]
Message-ID: <41E9F551.3060506@yahoo.com.au> (raw)
In-Reply-To: <1105851404.21576.4.camel@laptop.cunninghams>

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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2005-01-16  5:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  6:14 Bernard Blackham
2005-01-13  6:26 ` Nick Piggin
2005-01-13  8:56   ` Bernard Blackham
2005-01-13 10:14     ` Bernard Blackham
2005-01-15 10:16       ` Nick Piggin
2005-01-15 10:34         ` Nigel Cunningham
2005-01-15 10:40           ` Nick Piggin
2005-01-15 10:48             ` Nigel Cunningham
2005-01-15 11:01               ` Nick Piggin
2005-01-15 11:32                 ` Nigel Cunningham
2005-01-15 12:40                 ` Bernard Blackham
2005-01-15 12:53                   ` Bernard Blackham
2005-01-16  3:55                     ` Nick Piggin
2005-01-16  4:36                       ` Bernard Blackham
2005-01-16  4:56                         ` Nigel Cunningham
2005-01-16  5:02                           ` Nick Piggin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41E9F551.3060506@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=bernard@blackham.com.au \
    --cc=linux-mm@kvack.org \
    --cc=ncunningham@linuxmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox