From: "Rus V. Brushkoff" <rus@SoyuzKT.Od.UA>
To: linux-mm@kvack.org
Subject: 'cat /proc/interrupts' memleak
Date: Fri, 2 Feb 2007 22:07:37 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.64.0702022205470.17599@Soyuz-KT.TeNet.Odessa.UA> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 165 bytes --]
Hi,
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.
TIA
Rus
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 14585 bytes --]
next reply other threads:[~2007-02-02 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 20:07 Rus V. Brushkoff [this message]
2007-02-06 6:29 ` Andrew Morton
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=Pine.LNX.4.64.0702022205470.17599@Soyuz-KT.TeNet.Odessa.UA \
--to=rus@soyuzkt.od.ua \
--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