From: John Wilkins <john.wilkins@inktank.com>
Date: Thu, 18 Apr 2013 01:25:06 +0000 (-0700)
Subject: doc: Moved CPU profiling from operations to troubleshooting.
X-Git-Tag: v0.61~170
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=9e9bd2d8b1551fbb6e459000eacad5c8e7e6d7e4;p=ceph.git

doc: Moved CPU profiling from operations to troubleshooting.

Signed-off-by: John Wilkins <john.wilkins@inktank.com>
---

diff --git a/doc/rados/operations/cpu-profiling.rst b/doc/rados/operations/cpu-profiling.rst
deleted file mode 100644
index e46c5cab5942..000000000000
--- a/doc/rados/operations/cpu-profiling.rst
+++ /dev/null
@@ -1,67 +0,0 @@
-===============
- CPU Profiling
-===============
-
-If you built Ceph from source and compiled Ceph for use with `oprofile`_
-you can profile Ceph's CPU usage. See `Installing Oprofile`_ for details.
-
-
-Initializing oprofile
-=====================
-
-The first time you use ``oprofile`` you need to initialize it. Locate the
-``vmlinux`` image corresponding to the kernel you are now running. :: 
-
-	ls /boot
-	sudo opcontrol --init
-	sudo opcontrol --setup --vmlinux={path-to-image} --separate=library --callgraph=6
-
-
-Starting oprofile
-=================
-
-To start ``oprofile`` execute the following command:: 
-
-	opcontrol --start
-
-Once you start ``oprofile``, you may run some tests with Ceph. 
-
-
-Stopping oprofile
-=================
-
-To stop ``oprofile`` execute the following command:: 
-
-	opcontrol --stop
-	
-	
-Retrieving oprofile Results
-===========================
-
-To retrieve the top ``cmon`` results, execute the following command:: 
-
-	opreport -gal ./cmon | less	
-	
-
-To retrieve the top ``cmon`` results with call graphs attached, execute the
-following command:: 
-
-	opreport -cal ./cmon | less	
-	
-.. important:: After reviewing results, you should reset ``oprofile`` before
-   running it again. Resetting ``oprofile`` removes data from the session 
-   directory.
-
-
-Resetting oprofile
-==================
-
-To reset ``oprofile``, execute the following command:: 
-
-	sudo opcontrol --reset   
-   
-.. important:: You should reset ``oprofile`` after analyzing data so that 
-   you do not commingle results from different tests.
-
-.. _oprofile: http://oprofile.sourceforge.net/about/
-.. _Installing Oprofile: ../../../install/cpu-profiler
diff --git a/doc/rados/troubleshooting/cpu-profiling.rst b/doc/rados/troubleshooting/cpu-profiling.rst
new file mode 100644
index 000000000000..e46c5cab5942
--- /dev/null
+++ b/doc/rados/troubleshooting/cpu-profiling.rst
@@ -0,0 +1,67 @@
+===============
+ CPU Profiling
+===============
+
+If you built Ceph from source and compiled Ceph for use with `oprofile`_
+you can profile Ceph's CPU usage. See `Installing Oprofile`_ for details.
+
+
+Initializing oprofile
+=====================
+
+The first time you use ``oprofile`` you need to initialize it. Locate the
+``vmlinux`` image corresponding to the kernel you are now running. :: 
+
+	ls /boot
+	sudo opcontrol --init
+	sudo opcontrol --setup --vmlinux={path-to-image} --separate=library --callgraph=6
+
+
+Starting oprofile
+=================
+
+To start ``oprofile`` execute the following command:: 
+
+	opcontrol --start
+
+Once you start ``oprofile``, you may run some tests with Ceph. 
+
+
+Stopping oprofile
+=================
+
+To stop ``oprofile`` execute the following command:: 
+
+	opcontrol --stop
+	
+	
+Retrieving oprofile Results
+===========================
+
+To retrieve the top ``cmon`` results, execute the following command:: 
+
+	opreport -gal ./cmon | less	
+	
+
+To retrieve the top ``cmon`` results with call graphs attached, execute the
+following command:: 
+
+	opreport -cal ./cmon | less	
+	
+.. important:: After reviewing results, you should reset ``oprofile`` before
+   running it again. Resetting ``oprofile`` removes data from the session 
+   directory.
+
+
+Resetting oprofile
+==================
+
+To reset ``oprofile``, execute the following command:: 
+
+	sudo opcontrol --reset   
+   
+.. important:: You should reset ``oprofile`` after analyzing data so that 
+   you do not commingle results from different tests.
+
+.. _oprofile: http://oprofile.sourceforge.net/about/
+.. _Installing Oprofile: ../../../install/cpu-profiler