From: "J.R. Mauro" <jrm8005@gmail.com>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to check for memory leaks
Date: Mon, 8 Dec 2008 20:38:39 -0500 [thread overview]
Message-ID: <3aaafc130812081738o41c720f4kaf2a3ce611747b8@mail.gmail.com> (raw)
In-Reply-To: <c62985530812081433o5125f08gb7cad0d33a1b4104@mail.gmail.com>
On Mon, Dec 8, 2008 at 5:33 PM, Frédéric Weisbecker <fweisbec@gmail.com> wrote:
> 2008/12/8 Larry Finger <Larry.Finger@lwfinger.net>:
>> 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
Is this the driver in the staging tree or a different one?
>> 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.
>>
>> Thanks,
>>
>> Larry
>
>
> Hi,
>
> You could have a look on kmemleak: http://www.procode.org/kmemleak/
> It's up to date version is on the arm development git branch (topic kmemleak):
> http://www.linux-arm.org/git?p=linux-2.6.git;a=summary
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2008-12-09 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 22:18 Larry Finger
2008-12-08 22:33 ` Frédéric Weisbecker
2008-12-09 1:38 ` J.R. Mauro [this message]
2008-12-09 1:45 ` Larry Finger
2008-12-09 1:49 ` Larry Finger
2008-12-09 8:55 ` Hinko Kocevar
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=3aaafc130812081738o41c720f4kaf2a3ce611747b8@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=fweisbec@gmail.com \
--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
all inboxes | Powered by JetHome®