From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
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 11:38:41 -0400 [thread overview]
Message-ID: <20080711153841.GA14359@Krystal> (raw)
In-Reply-To: <20080710210543.1945415d@linux360.ro>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
Hi Eduard,
Did you have a look at the new tracepoints infrastructure ? I think it
could simplify your patchset a _lot_ !
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.
Regards,
Mathieu
* Eduard - Gabriel Munteanu (eduard.munteanu@linux360.ro) wrote:
> Hi everybody,
>
> I'd like to hear your opinion regarding kmemtrace and SL*B hooks.
>
> This is just a RFC, it's not intended to be merged yet. The userspace
> app is not included.
>
> BTW, there may be some whitespace errors, but disregard them for now,
> they will be fixed.
>
> Cheers,
> Eduard
>
>
> Eduard - Gabriel Munteanu (5):
> kmemtrace: Core implementation.
> Add new GFP flag __GFP_NOTRACE.
> kmemtrace: SLAB hooks.
> kmemtrace: SLUB hooks.
> kmemtrace: SLOB hooks.
>
> MAINTAINERS | 6 ++
> include/linux/gfp.h | 1 +
> include/linux/kmemtrace.h | 110 +++++++++++++++++++++++
> include/linux/slab_def.h | 16 +++-
> include/linux/slub_def.h | 9 ++-
> init/main.c | 2 +
> lib/Kconfig.debug | 4 +
> mm/Makefile | 2 +-
> mm/kmemtrace.c | 213 +++++++++++++++++++++++++++++++++++++++++++++
> mm/slab.c | 35 ++++++--
> mm/slob.c | 37 +++++++--
> mm/slub.c | 49 +++++++++--
> 12 files changed, 460 insertions(+), 24 deletions(-)
> create mode 100644 include/linux/kmemtrace.h
> create mode 100644 mm/kmemtrace.c
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-11 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 18:05 [RFC PATCH 0/5] kmemtrace RFC patch series Eduard - Gabriel Munteanu
2008-07-11 8:25 ` Pekka Enberg
2008-07-11 8:25 ` Pekka Enberg
2008-07-11 20:20 ` Eduard - Gabriel Munteanu
2008-07-11 20:20 ` Eduard - Gabriel Munteanu
2008-07-11 15:38 ` Mathieu Desnoyers [this message]
2008-07-11 20:11 ` Eduard - Gabriel Munteanu
2008-07-11 20:11 ` Eduard - Gabriel Munteanu
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=20080711153841.GA14359@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.