linux-kernel - Re: [PATCH] tracing/kmemtrace: normalize the raw tracer event to the unified tracing API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Dec 2008 09:49:24 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	mingo@...e.hu
Subject: Re: [PATCH] tracing/kmemtrace: normalize the raw tracer event to
	the unified tracing API

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/