From: William Lee Irwin III <wli@holomorphy.com>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: linux-ia64@vger.kernel.org, davidm@napali.hpl.hp.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.7, ia64] continual memory leak at ~102kB/s...
Date: Fri, 6 Aug 2004 07:54:51 -0700 [thread overview]
Message-ID: <20040806145451.GI17188@holomorphy.com> (raw)
In-Reply-To: <20029.1091803458@www55.gmx.net>
On Fri, Aug 06, 2004 at 04:44:18PM +0200, Daniel Blueman wrote:
> When running 2.6.7 on a generic ia64 system, I see memory being leaked in
> the kernel. Most of the fancy (preempt, hot-plug procs, ...) features are
> disabled, and the system in a quiescent state [1].
> /proc/meminfo shows the memory as unaccounted for [2], so it seems likely it
> has been kmalloc()d somehere. A small script shows memory disappearing at
> 102kB/s [3].
> Anyone else seen this on ia64?
Could you dump /proc/slabinfo?
-- wli
next prev parent reply other threads:[~2004-08-06 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 14:44 [2.6.7, ia64] continual memory leak at ~102kB/s Daniel Blueman
2004-08-06 14:54 ` William Lee Irwin III [this message]
2004-08-09 9:22 ` Daniel Blueman
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=20040806145451.GI17188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=daniel.blueman@gmx.net \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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