--- .../process/debugging/userspace_debugging_guide.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Documentation/process/debugging/userspace_debugging_guide.rst b/Documentation/process/debugging/userspace_debugging_guide.rst index a7c94407bcae..61d7ee968687 100644 --- a/Documentation/process/debugging/userspace_debugging_guide.rst +++ b/Documentation/process/debugging/userspace_debugging_guide.rst @@ -114,9 +114,10 @@ For the full documentation see `<https://kernelshark.org/Documentation.html>`__ Perf & alternatives ------------------- -The tools mentioned above provide ways to inspect kernel code, results, variable values, etc. -Sometimes you have to find out first where to look and for those cases, a box of -performance tracking tools can help you to frame the issue. +The tools mentioned above provide ways to inspect kernel code, results, +variable values, etc. Sometimes you have to find out first where to look and +for those cases, a box of performance tracking tools can help you to frame the +issue. Why should you do a performance analysis? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -134,8 +135,8 @@ How to do a simple analysis with linux tools? For the start of a performance analysis, you can start with the usual tools like: -- ``top`` / ``htop`` / ``atop`` (*get an overview of the system load, see spikes on - specific processes*) +- ``top`` / ``htop`` / ``atop`` (*get an overview of the system load, see + spikes on specific processes*) - ``mpstat -P ALL`` (*look at the load distribution among CPUs*) - ``iostat -x`` (*observe input and output devices utilization and performance*) - ``vmstat`` (*overview of memory usage on the system*) -- 2.25.1 --6zqfebw3lp2d5uji--
