From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Free pages leaking in 2.5.64?
Date: Wed, 12 Mar 2003 13:50:18 +1300 [thread overview]
Message-ID: <1047430217.2288.7.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <20030311162552.7f78e764.akpm@digeo.com>
Hi.
Thanks for the reply. I hadn't looked at the hot/cold stuff before. I
sussed it out this morning and added a condition to the test for
refilling the pcp arrays, stopping them from being refilled during a
suspend/resume cycle. Now everything works fine in that area for me.
I'll check that there aren't any other calls to refill the pcp arrays,
so I can be sure it will work with interrupts enabled and whenever smp
support is added to swsusp.
Now I just have to get the image written and read back and switch from
using page flags to dynamically allocated bitmaps, as I said I would.
Thanks again for the reply and regards,
Nigel
On Wed, 2003-03-12 at 13:25, Andrew Morton wrote:
> Nigel Cunningham <ncunningham@clear.net.nz> wrote:
> >
> > Hi all.
> >
> > I've come across the following problem in 2.5.64. Here's example output.
> > The header is one page - all messages only have a single call to
> > get_zeroed_page between the printings and the same code works as
>
> nr_free_pages() does not account for the pages in the per-cpu head arrays.
>
> You can make the numbers look right via drain_local_pages(), but that is only
> 100% reliable on uniprocessor with interrupts disabled.
>
--
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:[~2003-03-12 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 10:03 Nigel Cunningham
2003-03-12 0:25 ` Andrew Morton
2003-03-12 0:50 ` Nigel Cunningham [this message]
2003-03-12 0:50 ` Nigel Cunningham
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=1047430217.2288.7.camel@laptop-linux.cunninghams \
--to=ncunningham@clear.net.nz \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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