linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Linux SLAB allocator issue
Date: Tue, 6 Jun 2006 16:58:13 -0400	[thread overview]
Message-ID: <4ae3c140606061358j140eec9fl45e22f8a9e673215@mail.gmail.com> (raw)

Hi,

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?

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?

Thanks,
Xin

             reply	other threads:[~2006-06-06 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-06 20:58 Xin Zhao [this message]
2006-06-07 12:16 ` Linux SLAB allocator issue Pekka Enberg
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=4ae3c140606061358j140eec9fl45e22f8a9e673215@mail.gmail.com \
    --to=uszhaoxin@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).