From: John Wilkins <john.wilkins@inktank.com>
Date: Tue, 22 Oct 2013 20:22:17 +0000 (-0700)
Subject: doc: Moved CPU Profiler docs to dev.
X-Git-Tag: v0.73~28^2~37
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=8a36503879fd4577bb69dab594deac1055190654;p=ceph.git

doc: Moved CPU Profiler docs to dev.

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

diff --git a/doc/dev/cpu-profiler.rst b/doc/dev/cpu-profiler.rst
new file mode 100644
index 000000000000..d7a77feb88cb
--- /dev/null
+++ b/doc/dev/cpu-profiler.rst
@@ -0,0 +1,54 @@
+=====================
+ Installing Oprofile
+=====================
+
+The easiest way to profile Ceph's CPU consumption is to use the `oprofile`_
+system-wide profiler.
+
+.. _oprofile: http://oprofile.sourceforge.net/about/
+
+Installation
+============
+
+If you are using a Debian/Ubuntu distribution, you can install ``oprofile`` by
+executing the following::
+
+	sudo apt-get install oprofile oprofile-gui
+	
+
+Compiling Ceph for Profiling
+============================
+
+To compile Ceph for profiling, first clean everything. :: 
+
+	make distclean
+	
+Then, export the following settings so that you can see callgraph output. :: 
+
+	export CFLAGS="-fno=omit-frame-pointer -O2 -g"
+
+Finally, compile Ceph. :: 
+
+	./autogen.sh
+	./configure
+	make
+
+You can use ``make -j`` to execute multiple jobs depending upon your system. For
+example::
+
+	make -j4
+
+
+Ceph Configuration 
+==================
+
+Ensure that you disable ``lockdep``. Consider setting logging to 
+levels appropriate for a production cluster. See `Ceph Logging and Debugging`_ 
+for details.
+
+.. _Ceph Logging and Debugging: ../../rados/troubleshooting/log-and-debug
+
+See the `CPU Profiling`_ section of the RADOS Troubleshooting documentation for details on using Oprofile.
+
+
+.. _CPU Profiling: ../../rados/troubleshooting/cpu-profiling
\ No newline at end of file
diff --git a/doc/install/cpu-profiler.rst b/doc/install/cpu-profiler.rst
deleted file mode 100644
index d7a77feb88cb..000000000000
--- a/doc/install/cpu-profiler.rst
+++ /dev/null
@@ -1,54 +0,0 @@
-=====================
- Installing Oprofile
-=====================
-
-The easiest way to profile Ceph's CPU consumption is to use the `oprofile`_
-system-wide profiler.
-
-.. _oprofile: http://oprofile.sourceforge.net/about/
-
-Installation
-============
-
-If you are using a Debian/Ubuntu distribution, you can install ``oprofile`` by
-executing the following::
-
-	sudo apt-get install oprofile oprofile-gui
-	
-
-Compiling Ceph for Profiling
-============================
-
-To compile Ceph for profiling, first clean everything. :: 
-
-	make distclean
-	
-Then, export the following settings so that you can see callgraph output. :: 
-
-	export CFLAGS="-fno=omit-frame-pointer -O2 -g"
-
-Finally, compile Ceph. :: 
-
-	./autogen.sh
-	./configure
-	make
-
-You can use ``make -j`` to execute multiple jobs depending upon your system. For
-example::
-
-	make -j4
-
-
-Ceph Configuration 
-==================
-
-Ensure that you disable ``lockdep``. Consider setting logging to 
-levels appropriate for a production cluster. See `Ceph Logging and Debugging`_ 
-for details.
-
-.. _Ceph Logging and Debugging: ../../rados/troubleshooting/log-and-debug
-
-See the `CPU Profiling`_ section of the RADOS Troubleshooting documentation for details on using Oprofile.
-
-
-.. _CPU Profiling: ../../rados/troubleshooting/cpu-profiling
\ No newline at end of file
diff --git a/doc/rados/troubleshooting/cpu-profiling.rst b/doc/rados/troubleshooting/cpu-profiling.rst
index e46c5cab5942..159f7998dcb9 100644
--- a/doc/rados/troubleshooting/cpu-profiling.rst
+++ b/doc/rados/troubleshooting/cpu-profiling.rst
@@ -64,4 +64,4 @@ To reset ``oprofile``, execute the following command::
    you do not commingle results from different tests.
 
 .. _oprofile: http://oprofile.sourceforge.net/about/
-.. _Installing Oprofile: ../../../install/cpu-profiler
+.. _Installing Oprofile: ../../../dev/cpu-profiler