summaryrefslogtreecommitdiff
path: root/2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex
diff options
context:
space:
mode:
Diffstat (limited to '2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex')
-rw-r--r--2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex30
1 files changed, 30 insertions, 0 deletions
diff --git a/2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex b/2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex
new file mode 100644
index 0000000..8d51265
--- /dev/null
+++ b/2005/flow-accounting-ols2005/OLS2005/prasad/prasad-abstract.tex
@@ -0,0 +1,30 @@
+
+% Registration Locating system problems using dynamic
+% instrumentation
+% Vara Prasad (varap@us.ibm.com)
+
+It is often difficult to diagnose complex
+problems without multiple rebuilds and
+reboots. Even in a simple setup, the problem
+can touch various layers of the application
+and operating system. Diagnosis is even more
+difficult in complex, multi-tiered systems. As
+Linux is deployed in these environments, it is
+becoming more important to have facilities to
+locate and identify such problems.
+
+Using the kprobes infrastructure, SystemTAP is
+being developed to dynamically instrument the
+kernel and user applications. SystemTAP
+instrumentation incurs low overhead when
+enabled, and zero overhead when disabled.
+SystemTAP provides facilities to define
+instrumentation points in a high-level
+language, and to aggregate and analyze the
+instrumentation data. Details of the SystemTAP
+architecture and implementation are presented,
+along with examples of solving problems in the
+production environments.
+
+
+
personal git repositories of Harald Welte. Your mileage may vary