From: Pekka J Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: SLUB: Support for statistics to help analyze allocator behavior
Date: Wed, 6 Feb 2008 00:19:14 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.64.0802060015420.20750@sbz-30.cs.Helsinki.FI> (raw)
In-Reply-To: <Pine.LNX.4.64.0802051355270.14665@schroedinger.engr.sgi.com>
Hi Christoph,
On Tue, 5 Feb 2008, Pekka Enberg wrote:
> > > We could do that.... Any idea how to display that kind of information in a
> > > meaningful way. Parameter conventions for slabinfo?
> >
> > We could just print out one total summary and one summary for each CPU (and
> > maybe show % of total allocations/fees. That way you can immediately spot if
> > some CPUs are doing more allocations/freeing than others.
On Tue, 5 Feb 2008, Christoph Lameter wrote:
> Ok that would work for small amounts of cpus. Note that we are moving
> to quad core, many standard enterprise servers already have 8 and will
> likely have 16 next year. Our machine can have thousands of processors
> (new "practical" limit is 4k cpus although we could reach 16k cpus
> easily). I was a bit scared to open that can of worms.
I can see why. I think we can change the format summary a bit and have one
line per CPU only:
Allocation Deallocation
Page Add Remove RemoveObj/ Page Add Remove RemoveObj/
CPU Fast Slow Alloc Partial Partial SlabFrozen Fast Slow Alloc Partial Partial SlabFrozen
16000 111953360 1044 272 25 86 350 111946981 7423 264 325 264 4832
In addition, we can probably add some sort of option for determining how
many CPUs you're interested in seeing (sorted by CPUs that have most the
activity first).
Pekka
--
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:[~2008-02-05 22:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 6:20 Christoph Lameter
2008-02-05 7:24 ` Pekka J Enberg
2008-02-05 7:49 ` Eric Dumazet
2008-02-05 7:54 ` Pekka J Enberg
2008-02-05 18:08 ` Christoph Lameter
2008-02-05 18:55 ` Eric Dumazet
2008-02-05 19:07 ` Christoph Lameter
2008-02-05 18:05 ` Christoph Lameter
2008-02-05 20:20 ` Pekka Enberg
2008-02-05 21:58 ` Christoph Lameter
2008-02-05 22:19 ` Pekka J Enberg [this message]
2008-02-06 8:19 ` Andrew Morton
2008-02-06 19:01 ` Christoph Lameter
2008-02-06 21:00 ` SLUB: statistics improvements Christoph Lameter
2008-02-06 21:40 ` Eric Dumazet
2008-02-06 22:10 ` 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.0802060015420.20750@sbz-30.cs.Helsinki.FI \
--to=penberg@cs.helsinki.fi \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--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