linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Seger <Mark.Seger@hp.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: SLUB
Date: Thu, 27 Dec 2007 09:22:03 -0500	[thread overview]
Message-ID: <4773B50B.6060206@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712211338380.3795@schroedinger.engr.sgi.com>

Now that I've had some more time to think about this and play around 
with the slabinfo tool I fear my problem had getting my head wrapped 
around the terminology, but that's my problem.  Since there are entries 
called object_size, objs_per_slab and slab_size I would have thought 
that object_size*objects_per_slab=slab_size but that clearly isn't the 
case.  Since slabs are allocated in pages, the actual size of the slabs 
is always a multiple of the page_size (actually by a power of 2) and 
that's why I see calculations in slabinfo like page_size << order, but I 
guess I'm still not sure what the  actual definition of 'order' actually is.

Anyhow, when I run slabinfo and see the following entry

Slabcache: skbuff_fclone_cache   Aliases:  0 Order :  0 Objects: 25
** Hardware cacheline aligned

Sizes (bytes)     Slabs              Debug                Memory
------------------------------------------------------------------------
Object :     420  Total  :       4   Sanity Checks : Off  Total:   16384
SlabObj:     448  Full   :       0   Redzoning     : Off  Used :   10500
SlabSiz:    4096  Partial:       0   Poisoning     : Off  Loss :    5884
Loss   :      28  CpuSlab:       4   Tracking      : Off  Lalig:     700
Align  :       0  Objects:       9   Tracing       : Off  Lpadd:     256

according to the entries under /sys/slabs/skbuff_fclone_cache it looks 
like the slab_size field is being reported above as 'SlabObj' and 
objs_per_slab is being reported as 'Objects' and as I mentioned above, 
SlabSiz is based on 'order'.

Anyhow, as I understand what's going on at a very high level, memory is 
reserved for use as slabs (which themselves are multiples of pages) and 
processes allocate objects from within slabs as they need them.  
Therefore the 2 high-level numbers that seem of interest from a memory 
usage perspective are the memory allocated and the amount in use.  I 
think these are the "Total" and "Used" fields in slabinfo.

Total = page_size << order

As for 'Used' that looks to be a straight calculation of objects * 
object_size

The Slabs field in /proc/meminfo is the total of the individual 'Total's...

Stay tuned and at some point I'll have support in collectl for reporting 
total/allocated usage by slab in collectl, though perhaps I'll post a 
'proposal' first in the hopes of getting some constructive feedback as I 
want to present useful information rather than that columns of numbers.

-mark


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-12-27 14:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 15:06 SLUB Mark Seger
2007-12-20 19:44 ` SLUB Christoph Lameter
2007-12-20 23:36   ` SLUB Mark Seger
2007-12-21  1:09     ` SLUB Mark Seger
2007-12-21  1:27       ` SLUB Mark Seger
2007-12-21 21:41       ` SLUB Christoph Lameter
2007-12-27 14:22         ` Mark Seger [this message]
2007-12-27 15:59           ` SLUB Mark Seger
2007-12-27 19:43             ` SLUB Christoph Lameter
2007-12-27 19:57               ` SLUB Mark Seger
2007-12-27 19:58                 ` SLUB Christoph Lameter
2007-12-27 20:17                   ` SLUB Mark Seger
2007-12-27 20:55                   ` SLUB Mark Seger
2007-12-27 20:59                     ` SLUB Christoph Lameter
2007-12-27 23:49                       ` collectl and the new slab allocator [slub] statistics Mark Seger
2007-12-27 23:52                         ` Christoph Lameter
2007-12-28 15:10                           ` Mark Seger
2007-12-31 18:30                             ` Mark Seger
2007-12-27 19:40           ` SLUB Christoph Lameter
2007-12-27 19:51             ` SLUB Mark Seger
2007-12-27 19:53               ` SLUB Christoph Lameter
2007-12-21 21:32     ` SLUB Christoph Lameter
2007-12-21 16:59   ` SLUB Mark Seger
2007-12-21 21:37     ` SLUB 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=4773B50B.6060206@hp.com \
    --to=mark.seger@hp.com \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.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