summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNeil Horman <nhorman@tuxdriver.com>2009-08-13 05:20:45 +0000
committerDavid S. Miller <davem@davemloft.net>2009-08-13 16:42:37 -0700
commit5a165657bef7c47e5ff4cd138f7758ef6278e87b (patch)
tree1fb410c2333353b3c36dfc8ac72b9f2b74945acb
parente9b3cc1b3779fe10a80de4c3e7404bd308d0eae3 (diff)
net: skb ftracer - Add config option to enable new ftracer (v3)
skb allocation / consumption corelator - Add config option This patch adds a Kconfig option to enable the addtition of the skb source tracer. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Kconfig | 10 ++++++++++ 1 file changed, 10 insertions(+) Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r--kernel/trace/Kconfig10
1 files changed, 10 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 019f380fd764..f09d7635c0e1 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -234,6 +234,16 @@ config BOOT_TRACER
You must pass in initcall_debug and ftrace=initcall to the kernel
command line to enable this on bootup.
+config SKB_SOURCES_TRACER
+ bool "Trace skb source information"
+ select GENERIC_TRACER
+ help
+ This tracer helps developers/sysadmins correlate skb allocation and
+ consumption. The idea being that some processes will primarily consume data
+ that was allocated on certain numa nodes. By being able to visualize which
+ nodes the data was allocated on, a sysadmin or developer can optimize the
+ scheduling of those processes to cut back on cross node chatter.
+
config TRACE_BRANCH_PROFILING
bool
select GENERIC_TRACER