| 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
| ||
|
Message-Id: <1291421609-14665-14-git-send-email-dhsharp@google.com> Date: Fri, 3 Dec 2010 16:13:27 -0800 From: David Sharp <dhsharp@...gle.com> To: rostedt@...dmis.org, linux-kernel@...r.kernel.org Cc: mrubin@...gle.com, David Sharp <dhsharp@...gle.com> Subject: [PATCH 13/15] small_traces: Add config option to shrink trace events. This option will remove several fields from trace events to reduce the payload size. Under heavy load, events can be produced faster than they can possibly be written to disk or sent on the network. Shrinking the payload size will enable fitting more traces in the ring buffer, which therefore enables tracing for longer periods, at the cost of losing some relatively unimportant details. Google-Bug-Id: 3224547 Signed-off-by: David Sharp <dhsharp@...gle.com> --- kernel/trace/Kconfig | 12 ++++++++++++ 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index ea37e2f..9c24fe5 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -403,6 +403,18 @@ config FUNCTION_PROFILER If in doubt, say N. +config SMALL_TRACES + bool "Shrink trace events" + default n + help + Minimize the size of trace events. Omits fields from trace event + header like preempt_count, and lock_depth. Chooses smaller + alternative event structures. Shrinking the payload size enables + fitting more traces in the ring buffer, which enables tracing for + longer periods when the buffer can not be read as fast as it is + filled, at the cost of losing some details. + + config FTRACE_MCOUNT_RECORD def_bool y depends on DYNAMIC_FTRACE -- 1.7.3.1 -- 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/
Powered by blists - more mailing lists