linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Skip Gaede <sgaede@attbi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Memory leak
Date: Fri, 21 Jun 2002 22:22:56 -0400	[thread overview]
Message-ID: <200206212222.56162.sgaede@attbi.com> (raw)
In-Reply-To: <200206200352.32895.sgaede@attbi.com>


On Thursday 20 June 2002 03:52, Skip Gaede wrote:
> Folks,
>
>
> I'm looking for a recipe on how to track where my memory
> is disappearing to. I am running kernel
> 2.4.19-pre10-ben0, patched for the nubus-pmac platform. I
> have 40 MB RAM and a 100 MB swap file on the local hard
> disk.
>
OK, I recompiled the kernel with CONFIG_DEBUG_SLAB. The
memory is being consumed by the size-2048 cache, which I
believe is being used for network traffic.

I have two scenarios:

1) boot the system off the local hard drive and run X -query
192.168.0.1

2) boot the kernel+initrd off the local hard drive and mount
root via NFS, then run X -query ...

In the first case, the 2048 cache works well. After 30
minutes of continuous network traffic,

size-2048      5   50  2048    3    25  1

In the second case, after only 15 minutes

size-2048   187 228  2048  94  114  1  (15 min)
size-2048   918 928  2048 460 464  1  (60 min)

So the number of active buffers is much higher and it
continues to grow. Does anyone have any idea as to why this
is happening, or how to debug it?

Thanks,
Skip

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-22  2:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  7:52 Memory leak Skip Gaede
2002-06-22  2:22 ` Skip Gaede [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 15:06 diekema_jon
2003-03-12 19:50 Memory Leak Aman
2003-03-12 20:29 ` Matt Porter

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=200206212222.56162.sgaede@attbi.com \
    --to=sgaede@attbi.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).