[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802060015420.20750@sbz-30.cs.Helsinki.FI>
Date: Wed, 6 Feb 2008 00:19:14 +0200 (EET)
From: Pekka J Enberg <penberg@...helsinki.fi>
To: Christoph Lameter <clameter@....com>
cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: SLUB: Support for statistics to help analyze allocator behavior
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists