mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <gl@dsa-ac.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6.17.4] slabinfo.buffer_head increases
Date: Mon, 10 Jul 2006 13:28:10 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0607101023450.27628@pcgl.dsa-ac.de> (raw)

Hi

I am obsering a steadily increasing buffer_head value in slabinfo under 
2.6.17.4. I searched the net / archives and didn't find anything 
directly relevant. Does anyone have an idea or how shall we debug it?

I first noticed this "feature" on a 2.6.17-rc5 based ARM-system, where if 
I stop some user-space applications, the number stop increasing.

I was also able to reproduce it on a SuSE-9.0 system, where I wasn't able 
to stop this growth even as I stopped all possible services. Then the 
process list looked like this:

  PID TTY      STAT   TIME COMMAND
    1 ?        S      0:00 init [5]  
    2 ?        SWN    0:00 [ksoftirqd/0]
    3 ?        SW     0:00 [watchdog/0]
    4 ?        SW<    0:00 [events/0]
    5 ?        SW<    0:00 [khelper]
    6 ?        SW<    0:00 [kthread]
    8 ?        SW<    0:00 [kblockd/0]
    9 ?        SW<    0:00 [kacpid]
   82 ?        SW<    0:00 [kseriod]
  108 ?        SW     0:00 [pdflush]
  109 ?        SW     0:00 [pdflush]
  110 ?        SW     0:00 [kswapd0]
  111 ?        SW<    0:00 [aio/0]
  721 ?        SW<    0:00 [kpsmoused]
  726 ?        SW<    0:00 [reiserfs/0]
 1560 ?        SW     0:00 [khpsbpkt]
 4015 ?        S      0:00 login -- gl     
 4016 tty3     S      0:00 /sbin/mingetty tty3
 4017 tty4     S      0:00 /sbin/mingetty tty4
 4018 tty5     S      0:00 /sbin/mingetty tty5
 4019 tty6     S      0:00 /sbin/mingetty tty6
 4480 ?        S      0:00 login -- root     
 5051 tty1     R      0:00 -bash
 5330 tty2     S      0:00 -bash
 5601 tty2     S      0:00 sleep 5
 5602 tty1     R      0:00 ps ax

the "sleep 5" comes from the script:

while true; do grep buffer_head /proc/slabinfo; sleep 5; done

Does it look like a memory leak? Here's a fragment of the output:

buffer_head         8110   8112     48   78    1 : tunables  120   60    0 : slabdata    104    104      0
buffer_head         8148   8190     48   78    1 : tunables  120   60    0 : slabdata    105    105      0
buffer_head         8144   8190     48   78    1 : tunables  120   60    0 : slabdata    105    105      0
buffer_head         8166   8190     48   78    1 : tunables  120   60    0 : slabdata    105    105      0
buffer_head         8181   8190     48   78    1 : tunables  120   60    0 : slabdata    105    105      0
buffer_head         8189   8190     48   78    1 : tunables  120   60    0 : slabdata    105    105      0
buffer_head         8226   8268     48   78    1 : tunables  120   60    0 : slabdata    106    106      0
buffer_head         8244   8268     48   78    1 : tunables  120   60    0 : slabdata    106    106      0
buffer_head         8240   8268     48   78    1 : tunables  120   60    0 : slabdata    106    106      0
buffer_head         8260   8268     48   78    1 : tunables  120   60    0 : slabdata    106    106      0
buffer_head         8304   8346     48   78    1 : tunables  120   60    0 : slabdata    107    107      0
buffer_head         8340   8346     48   78    1 : tunables  120   60    0 : slabdata    107    107      0
buffer_head         8332   8346     48   78    1 : tunables  120   60    0 : slabdata    107    107      0
buffer_head         8343   8346     48   78    1 : tunables  120   60    0 : slabdata    107    107      0

Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany

             reply	other threads:[~2006-07-10 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 11:28 Guennadi Liakhovetski [this message]
2006-07-10 12:19 ` Guennadi Liakhovetski
2006-09-06 11:48   ` Guennadi Liakhovetski
2006-09-12  2:47     ` Nick Piggin
2006-09-12  7:40       ` Guennadi Liakhovetski
2006-09-13  2:32         ` Nick Piggin

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.63.0607101023450.27628@pcgl.dsa-ac.de \
    --to=gl@dsa-ac.de \
    --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®