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>

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 019f380fd764c80354ed277cfc72b7a2e4906b19..f09d7635c0e1c6be2639e9bba06a3258bfdc86c9 100644 (file)
--- 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