From: Ralf Baechle <ralf@oss.sgi.com>
To: Krishna Kondaka <krishna@Sanera.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: Memory leaks in SMP MIPS linux 2.4.9?
Date: Wed, 28 Nov 2001 15:05:52 +1100 [thread overview]
Message-ID: <20011128150552.A27925@dea.linux-mips.net> (raw)
In-Reply-To: <200111280109.RAA17976@exceed2.sanera.net>; from krishna@Sanera.net on Tue, Nov 27, 2001 at 05:09:00PM -0800
On Tue, Nov 27, 2001 at 05:09:00PM -0800, Krishna Kondaka wrote:
> I suspect that there are some memory leaks in the SMP MIPS linux 2.4.9.
> I would like to know if any one found the root cause and fixed them.
See patch below for fix.
> I just ran the script for 3 hours are here is the diff between
> the out put of /proc/meminfo and /proc/slabinfo before and
> after the test run ( lines with "<" are before the test and
> lines with ">" are after the test)
(Try diff -u which generates much more human readable output.)
> When I did some investigation, it looked like d_lookup() is
> not finding /proc/meminfo and /proc/slabinfo in the dcache and
> it is doing d_alloc() to add these to the cache every time
> cat /proc/meminfo or cat /proc/slabinfo is done. This looked odd
> and I ran the same script on x86 based linux (running 2.4.2) and
> I did not see MemFree (or any other caches) changing after the
> test was run for an hour. I am not sure how this is architecture
> dependent.
These caches essentially keep growing until you run out of memory which
is when they'll be freed.
Ralf
--- linux.orig/include/asm-mips/mmu_context.h.orig Wed Nov 28 14:45:19 2001
+++ linux/include/asm-mips/mmu_context.h Wed Nov 28 14:47:37 2001
@@ -109,7 +109,10 @@
*/
extern inline void destroy_context(struct mm_struct *mm)
{
- /* Nothing to do. */
+#ifdef CONFIG_SMP
+ if (mm->context)
+ kfree((void *)mm->context);
+#endif
}
/*
next prev parent reply other threads:[~2001-11-28 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 1:09 Memory leaks in SMP MIPS linux 2.4.9? Krishna Kondaka
2001-11-28 4:05 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 4:31 Krishna Kondaka
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=20011128150552.A27925@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=krishna@Sanera.net \
--cc=linux-mips@oss.sgi.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