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 14:57:26 -0500 [thread overview]
Message-ID: <477403A6.6070208@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712271141390.30555@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Thu, 27 Dec 2007, Mark Seger wrote:
>
>
>> <-------- objects --------><----- slabs
>> -----><------ memory ------>
>> Slab Name Size In Use Avail Size Number Used Total
>> :0000008 8 2164 2560 4096 5 17312 20480
>>
>
> The right hand side is okay. Could you list all the slab names that are
> covered by :00008 on the left side (maybe separated by commas?) Having the
> :00008 there is ugly. slabinfo can show you a way how to get the names.
>
here's the challenge - I only want to use a single line per entry AND I
want all the columns to line up for easy reading (I don't want much do
I?). I'll have to do some experiments to see what might look better.
One thought is to list a 'primary' name (whatever that might mean) in
the left-hand column and perhaps line up the rest of the other names to
the right of the total. Another option could be to just repeat the line
with each slab entry but that also generates a lot of output and one of
the other notions behind collectl is to make it real easy to see what's
going on and repeating information can be confusing.
I'm assuming the way slabinfo gets the names (or at least the way I can
think of doing it) it so just look for entries in /sys/slab that are links.
>> There are all sorts of other ways to present the data such as percentages,
>> differences, etc. but this is more-or-less the way I did it in the past and
>> the information was useful. One could also argue that the real key
>> information here is Uses/Total and the rest is just window dressing and I
>> couldn't disagree with that either, but I do think it helps paint a more
>> complete picture.
>>
>
> I agree.
>
The neat thing about collectl is it's written in perl and contains lots
of switches and print statements. I can easily see additional switches
that might control how the information is printed, such as the 'node'
level allocations, but I figure that can come later.
-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>
next prev parent reply other threads:[~2007-12-27 19:57 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 ` Mark Seger [this message]
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=477403A6.6070208@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