Re: [PATCH 03/11] tracing: add soft disable for syscall events
From: Steven Rostedt
Date: Sat Jun 22 2013 - 07:45:51 EST
On Sat, 2013-06-22 at 13:08 +0800, Jovi Zhang wrote:
> > I would really like to make these smaller. They are made for every
> > system call, and I consider tracing to always be added overhead. I hate
> > it when we waste more memory for tracing as very few people use it
> > (compared to those that use Linux).
> > Is it possible to allocate this only when its first used?
> > -- Steve
> I think the answer is yes.
> Compare with link ftrace_event_file with static syscall_metadata, another option
> is put into structure trace_array, just like enabled_enter_syscalls and
> enabled_exit_syscalls BITMAP already in there
> (need change to dynamic allocated NR_syscalls array, just keep a
> pointer in trace_array).
> Then in this way, there don't have any extra size overhead for static
> but need to allocate a array with NR_syscalls elements when first use
> syscall tracing.
> which option do you prefer? steven.
Hey, if it only allocates when tracing is used, that's a big plus.
Tracing should be treated as a drug. Just like not allowing smoking in
public places, only punish the users, not those that want to breath
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/