From: Noor <noor.mubeen@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: slab cache size-32 objects growing forever
Date: Mon, 15 Aug 2005 13:20:03 +0530 [thread overview]
Message-ID: <76cfec0f0508150050256745a8@mail.gmail.com> (raw)
Hi,
I noticed that my system's (kernel 2.4.22) cache memory is fast reducing.
Its normal value is around 225M always.
its reduced to 175M over about 30 days and still going low.
I notice this unusual behaviour /proc/slabinfo.
total size-32 objects are very large.
about 300 objects of some type are being added to size-32
slab every 10min. There is no sign of any reduction.
size-32(DMA) 0 0 32 0 0 1
size-32 1979925 1979986 32 17522 17522
1) What kind of driver/kernel functions need to allocate such size-32 objects.
( for eg, if inode is for file inodes, size-32 is for ???)
2) Would it be possible to view the objects (any tool/utility for this)
3) What does this uncontrolled growth imply?
is someone requesting size-32 objects uncontrollably or
the Virtual Mem/slab is failing to release the cache.
or could it be both ?
3) If this is some driver's fault, what kind of flags/code
do i grep in driver dir, so that it will help me figure
a faulty driver (eg; SLAB_NO_REAP ?)
Thanks in advance.
Noor
(NB: newbie post)
reply other threads:[~2005-08-15 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=76cfec0f0508150050256745a8@mail.gmail.com \
--to=noor.mubeen@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