From: Till Kamppeter <till.kamppeter@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
lsb-discuss@lists.linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Fri, 12 Mar 2010 09:59:25 +0100 [thread overview]
Message-ID: <4B9A026D.1030806@gmail.com> (raw)
In-Reply-To: <20100309224347.GD5058@nowhere>
Can someone post this project idea on the ideas list today (marking that
it comes from a student). This could support our application as
mentoring organization.
Till
On 03/09/2010 11:43 PM, Frederic Weisbecker wrote:
> On Fri, Jan 29, 2010 at 12:51:59AM +0100, Till Kamppeter wrote:
>> No problem for students to suggest topics. We are not restricted to
>> wireless in terms of kernel. We support kernel projects in general.
>>
>> Please give your suggestion as answer to this e-mail, doing "Reply to
>> all", as I am not a kernel export, the other participants of this thread
>> should have a look at the student's project ideas and help finding
>> mentors.
>>
>> Till
>
>
>
> Ok, I hope it's not too late.
> Here is one subject that I would like to apply for:
>
>
> = Improving tracing in perf events / ftrace =
>
>
> Using trace events under perf events is still a young feature
> and needs various improvements.
>
> - Syscall events can carry only raw values and addresses.
> We need to make them "aware" of strings and structures contents
> from userspace.
>
> - Make function / function graph tracers usable by perf
>
> - Optimize tracing fast-path
>
> - Improve perf tools to better handle trace events scalability
>
> - Provide new perf tools that exploit trace events (scheduler
> migration analysis, etc...)
>
> - Implement a per context excluding (eg: exclude irqs, exclude functions, etc...)
>
> - There are always things to do there.
>
>
> Of course, each of these elements require a lot of work,
> so not all of them can be done in two months, and some
> of them can be started already before the summer.
>
>
next prev parent reply other threads:[~2010-03-12 8:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14 ` Luis R. Rodriguez
2010-02-04 4:52 ` Hin-Tak Leung
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23 ` Luis R. Rodriguez
2010-01-28 23:31 ` Greg KH
2010-01-28 23:41 ` Frederic Weisbecker
2010-01-28 23:51 ` Till Kamppeter
2010-03-09 22:43 ` Frederic Weisbecker
2010-03-12 8:12 ` Till Kamppeter
2010-03-18 3:40 ` Frederic Weisbecker
2010-03-12 8:59 ` Till Kamppeter [this message]
2010-03-12 9:38 ` [lsb-discuss] " Denis Silakov
2010-03-12 9:57 ` Till Kamppeter
2010-03-21 19:49 ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20 ` Johannes Berg
2010-02-01 18:01 ` Luis R. Rodriguez
2010-02-01 20:14 ` Maxim Levitsky
2010-02-01 20:17 ` david
2010-02-01 21:31 ` Maxim Levitsky
2010-02-03 9:23 ` Holger Schurig
2010-02-01 22:12 ` Nick Bowler
2010-02-02 4:25 ` Pat Erley
2010-02-03 9:25 ` Holger Schurig
2010-02-22 21:25 ` Luis R. Rodriguez
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=4B9A026D.1030806@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=mcgrof@gmail.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).