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: Sat, 15 Jan 2005 22:01:11 +1100	[thread overview]
Message-ID: <41E8F7F7.1010908@yahoo.com.au> (raw)
In-Reply-To: <1105786115.13918.9.camel@desktop.cunninghams>

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

Nigel Cunningham wrote:
> Hi Nick.
> 
> On Sat, 2005-01-15 at 21:40, Nick Piggin wrote:
> 

>>I've seen try to do order 8 allocations or something almost as
>>ridiculous. Atomic too.
> 
> 
> I believe you. But Bernard and I are dealing with Suspend2.
> 

Sorry, indeed you are. My mistake.

> 
>>Well, correction, I've seen _reports_. Never tried swsusp myself.
> 
> 
> :>
> 
>>I don't think a few order 0 and 1 allocations would do any harm
>>because otherwise every man and his dog would be having problems.
> 
> 
> Yes. Suspend2 does allocate a large number of zero order allocations for
> submitting I/O, but again, they're all freed prior to thawing frozen
> processes.
> 

Hmm. I wouldn't have thought that should be a problem. Obviously
something is just irritating a bug somewhere.

> 
>>>>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.
>>>
>>
>>It is basically a problem with one of my patches. I should be able
>>to fix it (although fixing swsusp would be nice too :) ).
> 
> 
> :> Nevertheless, if there's something suspend2 related I should fix...
> 

I wouldn't suspect so, but we'll see... How do I get my hands on
suspend2?

Also, Bernard, can you try running with the following patch and
see what output it gives when you reproduce the problem?

Thanks a lot,
Nick

[-- Attachment #2: kswapd-debug --]
[-- Type: text/plain, Size: 408 bytes --]

Index: linux-2.6/mm/vmscan.c
===================================================================
--- linux-2.6.orig/mm/vmscan.c	2005-01-15 21:54:24.579134294 +1100
+++ linux-2.6/mm/vmscan.c	2005-01-15 21:56:51.719355929 +1100
@@ -1182,6 +1182,7 @@
 		}
 		finish_wait(&pgdat->kswapd_wait, &wait);
 
+		printk("kswapd: balance_pgdat, order = %lu\n", order);
 		balance_pgdat(pgdat, 0, order);
 	}
 	return 0;

  reply	other threads:[~2005-01-15 11:01 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 [this message]
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

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=41E8F7F7.1010908@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