From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to check for memory leaks
Date: Tue, 09 Dec 2008 09:55:17 +0100 [thread overview]
Message-ID: <493E3275.4030905@cetrtapot.si> (raw)
In-Reply-To: <493D9D24.8080406@lwfinger.net>
Larry Finger wrote:
> What is the best way to check if there is a memory leak?
>
> If I start a ping running on my system using the rtl8187 driver, and nothing
> else active on my system, I see an increase in the "slab" value in /proc/meminfo
> of about 65 kB/minute. Is this indicative of a memory leak? When I run the same
> test with p54usb, the increase is only 20 kB/min.
>
Also see cat /proc/slabinfo (you need to compile some debugging feature to get access to
/proc/slabinfo).
HTTH,
Hinko
--
Hinko Kočevar, OSS developer
ČETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel ++386 (0) 4 280 66 03
e-mail hinko.kocevar@cetrtapot.si
http www.cetrtapot.si
prev parent reply other threads:[~2008-12-09 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 22:18 How to check for memory leaks Larry Finger
2008-12-08 22:33 ` Frédéric Weisbecker
2008-12-09 1:38 ` J.R. Mauro
2008-12-09 1:45 ` Larry Finger
2008-12-09 1:49 ` Larry Finger
2008-12-09 8:55 ` Hinko Kocevar [this message]
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=493E3275.4030905@cetrtapot.si \
--to=hinko.kocevar@cetrtapot.si \
--cc=Larry.Finger@lwfinger.net \
--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