From: "Stéphane ANCELOT" <sancelot@free.fr>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: detecting kernel mem leak
Date: Tue, 13 May 2008 10:50:51 +0200 [thread overview]
Message-ID: <4829566B.7090804@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0805071020210.3173@schroedinger.engr.sgi.com>
Hi,
I kept my kernel running with few applications for 5 days , doing
nothing more than backing up few kb of data on disk and refresh few X apps.
Ater five days the global memory available go down from 24Mb to 8Mb ...
The are some signifiant changes in slabinfo but now, I do not know where
to search ?
active_jobs :
proc_inode_cache : 150 -> 299
radix_tree_node : 807 -> 870
dentry: 4092 ->4249
buffer_head: 1138 -> 4824
pid_1: 64 -> 76
size-64 : 885 -> 944
memory BEFORE AFTER :
MemFree: 24324 kB.................8692Kb
Buffers: 3956 kB...............18740Kb
Cached: 34080 kB................34452Kb
Active: 131176 kB................147592Kb
Inactive: 26708 kB..................25440Kb
Slab: 4692 kB........4952kB
SReclaimable: 1480 kB ............. 1744kb
SUnreclaim: 3212 kB...............3208kb
in the ps tree only Xorg SHR memory growed from 5592 to 5612
next prev parent reply other threads:[~2008-05-13 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 9:41 detecting kernel mem leak sancelot
2008-04-29 12:46 ` 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 [this message]
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=4829566B.7090804@free.fr \
--to=sancelot@free.fr \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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.