From: sancelot@free.fr
To: linux-kernel@vger.kernel.org
Subject: detecting kernel mem leak
Date: Tue, 29 Apr 2008 11:41:34 +0200 [thread overview]
Message-ID: <1209462094.4816ed4e93977@imp.free.fr> (raw)
Hi,
I noticed the memory was growing without doing anything in my system ....after
some investigations , it looks like some kernel components may be involved in
this problem.
I would like to know if there is a way to monitor activity of memory (de)alloc
of the kernel in order to target which partof the system/kernel could do this..?
Best Regards
S.Ancelot
next reply other threads:[~2008-04-29 9:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 9:41 sancelot [this message]
2008-04-29 12:46 ` detecting kernel mem leak Pekka Enberg
2008-04-29 16:58 ` Christoph Lameter
[not found] ` <4821C526.8030901@free.fr>
2008-05-07 17:21 ` Christoph Lameter
2008-05-13 8:50 ` Stéphane ANCELOT
2008-05-13 19:45 ` Pekka Enberg
2008-05-15 10:58 ` Stéphane ANCELOT
2008-05-15 17:38 ` Christoph Lameter
2008-05-16 8:58 ` Stéphane ANCELOT
2008-05-16 18:50 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2008-05-13 10:26 Tomasz Chmielewski
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=1209462094.4816ed4e93977@imp.free.fr \
--to=sancelot@free.fr \
--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