linux-kernel - Re: [PATCH] tracing/filters: Defer pred allocation

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:	Mon, 31 Aug 2009 17:06:40 +0800
From:	Li Zefan <lizf@...fujitsu.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Tom Zanussi <tzanussi@...il.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing/filters: Defer pred allocation

Ingo Molnar wrote:
> * Li Zefan <lizf@...fujitsu.com> wrote:
> 
>> init_preds() allocates about 5392 bytes of memory (on x86_32) for
>> a TRACE_EVENT. With my config, at system boot total memory occupied
>> is:
>>
>> 	5392 * (642 + 15) == 3459KB
>>
>> 642 == cat available_events | wc -l
>> 15 == number of dirs in events/ftrace
>>
>> That's quite a lot, so we'd better defer memory allocation util
>> it's needed, that's when filter is used.
>>
>> Signed-off-by: Li Zefan <lizf@...fujitsu.com>
> 
> Applied, thanks!
> 
>> tracing/kprobe needs rebase after this patch..
> 
> You mean with many probes registered it has a lot of memory 

I think so, if filter is used.

> footprint? Instead of a rebase a merge of tracing/core into 
> tracing/kprobes would be less intrusive.
> 

Yeah, I meant this patch conflicts with some patches in
tracing/kprobe. :)

--
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/