From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: penberg@cs.helsinki.fi, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/5] kmemtrace RFC patch series
Date: Fri, 11 Jul 2008 23:11:38 +0300 [thread overview]
Message-ID: <20080711231138.5d3443b8@linux360.ro> (raw)
In-Reply-To: <20080711153841.GA14359@Krystal>
On Fri, 11 Jul 2008 11:38:41 -0400
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> Hi Eduard,
>
> Did you have a look at the new tracepoints infrastructure ? I think it
> could simplify your patchset a _lot_ !
Hi,
Yes, I did. In fact, I asked you to keep me Cc-ed, which you did.
> Basically, it removes the format string from markers and allows to
> pass complex structure pointers as arguments. It aims at simplifying
> the life of in-kernel tracers which would want to use the facility.
> Turning a marker implementation to tracepoints is really
> straightforward, for an example see :
>
> http://lkml.org/lkml/2008/7/9/569
>
> For the tracepoints patchset :
>
> http://lkml.org/lkml/2008/7/9/199
>
> I think much of include/linux/kmemtrace.h, which is really just
> wrappers around marker code, could then go away.
Basically, I want just as much to get rid of markers. I'm just waiting
for tracepoints to get closer to mainline.
Cheers,
Eduard
> Regards,
>
> Mathieu
--
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>
prev parent reply other threads:[~2008-07-11 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 18:05 Eduard - Gabriel Munteanu
2008-07-11 8:25 ` Pekka Enberg
2008-07-11 20:20 ` Eduard - Gabriel Munteanu
2008-07-11 15:38 ` Mathieu Desnoyers
2008-07-11 20:11 ` Eduard - Gabriel Munteanu [this message]
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=20080711231138.5d3443b8@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=penberg@cs.helsinki.fi \
/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