Messages in this thread | | | Subject | Re: [PATCH] tracing/kmemtrace: normalize the raw tracer event to the unified tracing API | From | Pekka Enberg <> | Date | Tue, 30 Dec 2008 09:49:24 +0200 |
| |
Hi Frederic,
On Mon, 2008-12-29 at 23:09 +0100, Frederic Weisbecker wrote: > Pekka, note that I would be pleased to add statistical tracing on > this tracer, but I would need a hashtable, or an array, or a list, or whatever > iterable to insert the data into the stat tracing api. > > But I don't know your projects about this... whether you wanted to use a section > or something else...
It really depends on what we're tracing. If we're interested in just the allocation hotspots, a section will do just fine. However, if we're tracing memory footprint, we need to take into store the object pointer returned from kmalloc() and kmem_cache_alloc() so we can update call-site statistics properly upon kfree().
So I suppose we need both, a section for per call-site statistics and a hash table for the object -> call-site mapping.
Pekka
| |