From: Christoph Lameter <clameter@sgi.com>
To: Mark Seger <Mark.Seger@hp.com>
Cc: linux-mm@kvack.org
Subject: Re: SLUB
Date: Thu, 20 Dec 2007 11:44:45 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0712201138280.30648@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <476A850A.1080807@hp.com>
On Thu, 20 Dec 2007, Mark Seger wrote:
> This past summer I released a tool on sourceforge called collectl - see
> http://collectl.sourceforge.net/ which does some pretty nifty system
> monitoring, one component of which is slabs. I finally got around to trying
> it out on a newer kernel and I picked 2.6.23 and lo and behold, it didn't work
> because /proc/slabinfo has disappeared to be replaced by /sys/slab. I've been
Yes. The information available about slabs is different now.
> The thing that is especially useful with collectl is that by monitoring slabs
> at the same time as monitoring cpu, processes, disk, network and more, you can
> get a very comprehensive picture of what's going on at any one time.
Good idea.
> My main purpose for writing to this list then becomes what would make the most
> sense to do with slabs with the new slub allocator? Should I simply report on
> these same fields? Are there others that make more sense? Do I need to read
> all 184 entries in /sys/slab and then all the entries under them? Clearly I
> want to do this efficiently and provide meaningful data at the same time.
You only need to read certain files that you need for the information you
want to display.
> Perhaps someone would like to take this discussion off-line with me and even
> collaborate with me on enhancements for slub in collectl?
I think we better keep it public (so that it goes into the archive). Here
a short description of the field in /sys/kernel/slab/<slabcache> that you
would need
-r--r--r-- 1 root root 4096 Dec 20 11:41 object_size
The size of an object. Subtract slab_size - object_size and you have the
per object overhead generated by alignements and slab metadata. Does not
change you only need to read this once.
-r--r--r-- 1 root root 4096 Dec 20 11:41 objects
Number of objects in use. This changes and you may want to monitor it.
-r--r--r-- 1 root root 4096 Dec 20 11:41 slab_size
Total memory used for a single object. Read this only once.
-r--r--r-- 1 root root 4096 Dec 20 11:41 slabs
Number of slab pages in use for this slab cache. May change if slab is
extended.
--
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-20 19:44 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 ` Christoph Lameter [this message]
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 ` 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=Pine.LNX.4.64.0712201138280.30648@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