From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Xin Zhao" <uszhaoxin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: Linux SLAB allocator issue
Date: Wed, 7 Jun 2006 15:16:58 +0300 [thread overview]
Message-ID: <84144f020606070516m4bccdecdr998941ee74744a83@mail.gmail.com> (raw)
In-Reply-To: <4ae3c140606061358j140eec9fl45e22f8a9e673215@mail.gmail.com>
On 6/6/06, Xin Zhao <uszhaoxin@gmail.com> wrote:
> I am trying to check how many slabs are used for inode_cache, but
> found that all slabs are added to slabs_full list, and slabs_partial
> is always empty. Even if the active object number does not exactly
> occupy all slabs.
>
> Does that mean Linux 2.6 remove the use of slabs_partial?
No. If slabs_partial is really empty, the number of active objects
should match the number of objects in a slab; otherwise you should see
an error message when you do cat /proc/slabinfo (see s_show in
mm/slab.c for details).
How are you verifying that the partial list is empty?
On 6/6/06, Xin Zhao <uszhaoxin@gmail.com> wrote:
> Another question, the constructor transfered to the
> kmem_cache_create() function is called for every object in a slab when
> it is created. Is this true? Is there any way to call back a function
> _only once_ when a new slab is allocated?
We don't have per-slab constructors. Only per-object. What do you need it for?
Pekka
next prev parent reply other threads:[~2006-06-07 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 20:58 Linux SLAB allocator issue Xin Zhao
2006-06-07 12:16 ` Pekka Enberg [this message]
2006-06-07 15:37 ` Xin Zhao
2006-06-07 17:41 ` Christoph Lameter
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=84144f020606070516m4bccdecdr998941ee74744a83@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.com \
/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).