From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
hugh.dickins@tiscali.co.uk
Subject: Re: Why half of slabs are not shown in /proc/slabinfo?
Date: Mon, 22 Jun 2009 09:56:22 +0300 [thread overview]
Message-ID: <1245653782.18751.12.camel@penberg-laptop> (raw)
In-Reply-To: <200906211530.13463.arvidjaar@mail.ru>
On Sun, 2009-06-21 at 15:30 +0400, Andrey Borzenkov wrote:
> On Sunday 21 of June 2009 15:26:15 Pekka Enberg wrote:
> > On Sun, Jun 21, 2009 at 10:52 AM, Andrey Borzenkov<arvidjaar@mail.ru>
> wrote:
> > > 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?
> >
> > Can you post the actual file listing of /sys/kernel/slab and the
> > contents of /proc/slabinfo?
>
> Sure.
>
> {pts/1}% ls -l /sys/kernel/slab
If you exclude all the symbolic links, the number of caches matches. As
Hugh already explained, SLUB merges caches which shows up like this in
the sysfs directory.
Pekka
next prev parent reply other threads:[~2009-06-22 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 7:52 Andrey Borzenkov
2009-06-21 11:26 ` Pekka Enberg
2009-06-21 11:30 ` Andrey Borzenkov
2009-06-22 6:56 ` Pekka Enberg [this message]
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=1245653782.18751.12.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=arvidjaar@mail.ru \
--cc=cl@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--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®