From: Christoph Lameter <clameter@sgi.com>
To: Mark Seger <Mark.Seger@hp.com>
Cc: linux-mm@kvack.org
Subject: Re: SLUB
Date: Fri, 21 Dec 2007 13:32:31 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0712211330350.3795@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <476AFC6C.3080903@hp.com>
On Thu, 20 Dec 2007, Mark Seger wrote:
> What I'm not sure about is how this maps to the old slab info. Specifically,
> I believe in the old model one reported on the size taken up by the slabs
> (number of slabs X number of objects/slab X object size). There was a second
> size for the actual number of objects in use, so in my report that looked like
> this:
>
> # <-----------Objects----------><---------Slab
> Allocation------>
> #Name InUse Bytes Alloc Bytes InUse Bytes Total
> Bytes
> nfs_direct_cache 0 0 0 0 0 0 0
> 0
> nfs_write_data 36 27648 40 30720 8 32768 8
> 32768
>
> the slab allocation was real memory allocated (which should come close to
> Slab: in /proc/meminfo, right?) for the slabs while the object bytes were
The real memory allocates can be deducated from the "slabs" field.
Multiply that by the order of the slab and you have the size of it.
The "objects" are the actual objects in current use.
> To get back to my original question, I'd like to make sure that I'm reporting
> useful information and not just data for the sake of it. In one of your
> postings I saw a report you had that showed:
>
> slubinfo - version: 1.0
> # name <objects> <order> <objsize> <slabs>/<partial>/<cpu> <flags>
> <nodes>
That report can be had using the slabinfo tool. See
Documentation/vm/slabinfo.c
> How useful is order, cpu, flags and nodes?
> Do people really care about how much memory is taken up by objects vs slabs?
> If not, I could see reporting for each slab:
> - object size
> - number objects
> - slab size
> - number of slabs
> - total memory (slab size X number of slabs)
> - whatever else people might think to be useful such as order, cpu, flags, etc
Sounds fine.
> Another thing I noticed is a number of the slabs are simply links to the same
> base name and is it sufficient to just report the base names and not those
> linked to it? Seems reasonable to me...
slabinfo reports it like that.
--
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>
next prev parent reply other threads:[~2007-12-21 21:32 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 ` SLUB Mark Seger
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 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0712211330350.3795@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Mark.Seger@hp.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