From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Why half of slabs are not shown in /proc/slabinfo?
Date: Sun, 21 Jun 2009 11:52:20 +0400 [thread overview]
Message-ID: <200906211152.25100.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 523 bytes --]
Mandriva kernel 2.6.30 using SLUB:
{pts/1}% grep SLUB /boot/config
CONFIG_SLUB_DEBUG=y
CONFIG_SLUB=y
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
Some of slabs (e.g. filp) are not shown in /proc/slabinfo; comparing
number of entries under /sys and slabinfo results in
{pts/0}% =ls -1 /sys/kernel/slab | grep -v : | wc -l
131
{pts/0}% wc -l /proc/slabinfo
68 /proc/slabinfo
{pts/0}%
so almost half of the all entries are missing. Is it expected or there
is something wrong here?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-06-21 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 7:52 Andrey Borzenkov [this message]
2009-06-21 11:26 ` Why half of slabs are not shown in /proc/slabinfo? Pekka Enberg
2009-06-21 11:30 ` Andrey Borzenkov
2009-06-22 6:56 ` Pekka Enberg
2009-06-23 17:43 ` Christoph Lameter
2009-06-21 11:36 ` Hugh Dickins
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=200906211152.25100.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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