From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Oliver Pinter <oliver.pntr@gmail.com>,
linux-mm@kvack.org, Christoph Lameter <clameter@sgi.com>,
linux-mm@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: SMP-related kernel memory leak
Date: Fri, 22 Feb 2008 08:52:06 +0100 [thread overview]
Message-ID: <e2e108260802212352y6df6dab8y26d6292b3b8cd813@mail.gmail.com> (raw)
In-Reply-To: <47BDEFB4.1010106@zytor.com>
On Thu, Feb 21, 2008 at 10:40 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> Oliver Pinter wrote:
> >>> I have added a new graph to
> >>> http://bugzilla.kernel.org/show_bug.cgi?id=9991, namely a graph
> >>> showing memory usage for a PAE-kernel booted with mem=1G and with a
> >>> minimized kernel config. The graph shows that memory usage increases
> >>> to a certain limit. Other tests have shown that this limit is
> >>> proportional to the amount of memory specified in mem=... This is not
> >>> a SLAB leak: as the numbers show, slab usage remains constant during
> >>> all tests.
> >>>
> >>> I'm puzzled by these results ...
>
> This sounds to me a lot like the quicklist PUD leak we had, which I
> thought had been fixed in recent kernels...
>
> It would be useful to know: does this happen with UP at all?
The behavior I see is consistent for both the 2.6.22.18 and the
2.6.24.2 kernels. The problem does not occur when I boot with
maxcpus=1 added to the kernel command line.
Bart Van Assche.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-22 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2e108260802190300k5b0f60f6tbb4f54997caf4c4e@mail.gmail.com>
[not found] ` <6101e8c40802191018t668faf3avba9beeff34f7f853@mail.gmail.com>
[not found] ` <e2e108260802192327v124a841dnc7d9b1c7e9057545@mail.gmail.com>
[not found] ` <6101e8c40802201342y7e792e70lbd398f84a58a38bd@mail.gmail.com>
[not found] ` <e2e108260802210048y653031f3r3104399f126336c5@mail.gmail.com>
[not found] ` <e2e108260802210800x5f55fee7ve6e768607d73ceb0@mail.gmail.com>
[not found] ` <6101e8c40802210821w626bc831uaf4c3f66fb097094@mail.gmail.com>
2008-02-21 16:25 ` SMP-related kernel memory leak Oliver Pinter
2008-02-21 21:40 ` H. Peter Anvin
2008-02-22 7:52 ` Bart Van Assche [this message]
2008-02-22 16:44 ` Oliver Pinter
2008-02-22 16:50 ` H. Peter Anvin
2008-02-22 23:12 ` Oliver Pinter
2008-02-22 23:22 ` H. Peter Anvin
2008-02-23 8:08 ` Bart Van Assche
2008-02-27 19:40 ` Christoph Lameter
2008-02-28 9:50 ` Bart Van Assche
2008-02-27 19:57 ` Christoph Lameter
2008-02-27 20:43 ` H. Peter Anvin
2008-02-22 12:06 ` Bart Van Assche
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=e2e108260802212352y6df6dab8y26d6292b3b8cd813@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=clameter@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-mm@kvack.org \
--cc=linux-mm@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).