From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>,
"Andi Kleen" <andi@firstfloor.org>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Tim Bird" <tim.bird@am.sony.com>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list
Date: Fri, 2 May 2008 23:01:41 +0300 [thread overview]
Message-ID: <20080502230141.1788f525@linux360.ro> (raw)
In-Reply-To: <84144f020805020800w765c5248r6dba93240230b983@mail.gmail.com>
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:
> 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.
next prev parent reply other threads:[~2008-05-02 20:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 17:42 [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list David Woodhouse
2008-04-30 17:44 ` [PATCH 1/1] " David Woodhouse
2008-05-01 9:55 ` Bart Van Assche
2008-05-01 10:05 ` David Woodhouse
2008-05-01 11:12 ` Bart Van Assche
2008-04-30 18:22 ` [PATCH 0/1] " Andi Kleen
2008-04-30 19:11 ` David Woodhouse
2008-06-23 17:22 ` Denys Vlasenko
2008-06-23 18:57 ` Sam Ravnborg
2008-06-23 19:12 ` Denys Vlasenko
2008-06-23 19:33 ` Sam Ravnborg
[not found] ` <48190B5F.9010505@am.sony.com>
[not found] ` <20080501095822.GL20451@one.firstfloor.org>
2008-05-01 10:02 ` David Woodhouse
2008-05-01 10:41 ` Andi Kleen
2008-05-02 15:00 ` Pekka Enberg
2008-05-02 20:01 ` Eduard - Gabriel Munteanu [this message]
2008-05-02 20:14 ` Andrew Morton
2008-05-02 20:33 ` Eduard - Gabriel Munteanu
2008-05-02 20:53 ` Andrew Morton
2008-05-03 22:24 ` Randy Dunlap
2008-05-05 1:52 ` Andrew Morton
2008-06-23 17:28 ` Denys Vlasenko
2008-06-23 17:45 ` Adrian Bunk
2008-06-23 18:19 ` Denys Vlasenko
2008-06-23 19:05 ` Tim Bird
2008-06-25 9:50 ` James Chapman
2008-06-25 15:41 ` Adrian Bunk
2008-04-30 18:26 ` Josh Boyer
2008-04-30 18:43 ` David Woodhouse
2008-04-30 18:45 ` Josh Boyer
2008-04-30 23:34 ` Adrian Bunk
2008-05-01 7:04 ` David Woodhouse
2008-05-02 11:58 ` Kristoffer Ericson
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=20080502230141.1788f525@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=penberg@cs.helsinki.fi \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.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