From: Bernard Blackham <bernard@blackham.com.au>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org
Subject: Re: Odd kswapd behaviour after suspending in 2.6.11-rc1
Date: Thu, 13 Jan 2005 16:56:27 +0800 [thread overview]
Message-ID: <20050113085626.GA5374@blackham.com.au> (raw)
In-Reply-To: <41E61479.5040704@yahoo.com.au>
On Thu, Jan 13, 2005 at 05:26:01PM +1100, Nick Piggin wrote:
> >I reverted the changes to mm/vmscan.c between 2.6.10 and 2.6.11-rc1
> >with the attached patch (applies forwards over the top of
> >2.6.11-rc1), and I no longer get any kswapd weirdness. Is there
> >something in here misbehaving?
>
> Hmm, it is likely to be the higher order watermarks change.
>
> Can you get a couple of Alt+SysRq+M traces during the time when
> kswapd is going crazy please?
Embarrasingly, I can't reproduce it at the moment. It was previously
occuring on every single suspend. Wondering if it's linked with swap
usage - I'll keep watching and provide some traces when it happens
again.
Thanks,
Bernard.
--
Bernard Blackham <bernard at blackham dot com dot au>
--
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>
next prev parent reply other threads:[~2005-01-13 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 6:14 Odd kswapd behaviour after suspending in 2.6.11-rc1 Bernard Blackham
2005-01-13 6:26 ` Nick Piggin
2005-01-13 8:56 ` Bernard Blackham [this message]
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
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=20050113085626.GA5374@blackham.com.au \
--to=bernard@blackham.com.au \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.