Hi,

I'm the student working on this. I have already implemented tracing for
SLAB, SLUB and SLOB, and patched relayfs to work early on (just after
kmem_cache_init() runs). Currently, I'm working on the userspace tool,
so much of the coding is largely finished.

I wanted to submit the relay stuff, but couldn't contact its maintainer.

If anyone wants to take a look, I could set up a git repo somewhere
(which has to be done anyway, at some point).


	Cheers,
	Eduard

On Fri, 2 May 2008 18:00:43 +0300
"Pekka Enberg" <penberg@cs.helsinki.fi> wrote:

quoted text
> Hi Andi,
> 
> On Thu, May 1, 2008 at 1:41 PM, Andi Kleen <andi@firstfloor.org>
> wrote:
> > > To a large extent, I agree. I certainly don't want to focus
> > > solely on code size; there's a lot more to embedded Linux than
> > > that. But it _is_
> >
> >  Not only code size, far more important is dynamic memory
> > consumption. [admittedly we right now lack a good instrumentation
> > framework for this]
> 
> There's a Google Summer of Code project going on now to implement such
> instrumentation:
> 
> http://code.google.com/soc/2008/linux/appinfo.html?csaid=E749E676AD70FBB0
> 
> So any suggestions/input on this is obviously welcome.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/