From: Andrew Morton <akpm@linux-foundation.org>
To: "Rus V. Brushkoff" <rus@SoyuzKT.Od.UA>
Cc: linux-mm@kvack.org
Subject: Re: 'cat /proc/interrupts' memleak
Date: Mon, 5 Feb 2007 22:29:27 -0800 [thread overview]
Message-ID: <20070205222927.095cb0d9.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702022205470.17599@Soyuz-KT.TeNet.Odessa.UA>
On Fri, 2 Feb 2007 22:07:37 +0200 (EET) "Rus V. Brushkoff" <rus@SoyuzKT.Od.UA> wrote:
> Doing in loop cat /proc/interrupts leaks memory in the system, which can
> be observerd by top. Seems like config depended, so one is attached.
I can't reproduce it here. Can you please monitor /proc/meminfo and
/proc/slabinfo, work out where the memory is going to?
--
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:[~2007-02-06 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 20:07 'cat /proc/interrupts' memleak Rus V. Brushkoff
2007-02-06 6:29 ` Andrew Morton [this message]
2007-02-06 8:09 ` Rus V. Brushkoff
2007-02-06 9:13 ` Rus V. Brushkoff
2007-02-06 9:22 ` Andrew Morton
2007-02-06 10:23 ` Rus V. Brushkoff
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=20070205222927.095cb0d9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rus@SoyuzKT.Od.UA \
/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.