[lkml]   [2008]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 1/4] kmemtrace: Core implementation.
On Tue, Jul 22, 2008 at 05:28:16PM -0400, Frank Ch. Eigler wrote:
> Eduard - Gabriel Munteanu <> writes:
> > kmemtrace provides tracing for slab allocator functions, such as kmalloc,
> > kfree, kmem_cache_alloc, kmem_cache_free etc.. Collected data is then fed
> > to the userspace application in order to analyse allocation hotspots,
> > internal fragmentation and so on, making it possible to see how well an
> > allocator performs, as well as debug and profile kernel code.
> > [...]
> It may make sense to mention in addition that this version of
> kmemtrace uses markers as the low-level hook mechanism, and this makes
> the data generated directly accessible to other tracing tools such as
> systemtap. Thank you!
> - FChE

Sounds like a good idea, but I'd like to get rid of markers and use
Mathieu Desnoyers' tracepoints instead. I'm just waiting for tracepoints
to get closer to inclusion in mainline/-mm.

It would be great if tracepoints completely replaced markers, so SystemTap
would use those instead.

However, if tracepoints are not ready when kmemtrace is to be merged,
I'll take your advice and mention markers and SystemTap.


 \ /
  Last update: 2008-07-23 02:55    [W:0.069 / U:2.976 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site