Section: System Administration (8)
Updated: October 2011
The readprofile command uses the /proc/profile information to print ascii data on standard output. The output is organized in three columns: the first is the number of clock ticks, the second is the name of the C function in the kernel where those many ticks occurred, and the third is the normalized `load' of the procedure, calculated as a ratio between the number of ticks and the length of the procedure. The output is filled with blanks to ease readability.
Browse the profiling buffer ordering by clock ticks:
readprofile | sort -nr | less
Print the 20 most loaded procedures:
readprofile | sort -nr +2 | head -20
Print only filesystem profile:
readprofile | grep _ext2
Look at all the kernel information, with ram addresses:
readprofile -av | less
Browse a `freezed' profile buffer for a non current kernel:
readprofile -p ~/profile.freeze -m /zImage.map.gz
Request profiling at 2kHz per CPU, and reset the profiling buffer:
sudo readprofile -M 20
readprofile only works with an 1.3.x or newer kernel, because /proc/profile changed in the step from 1.2 to 1.3
This program only works with ELF kernels. The change for a.out kernels is trivial, and left as an exercise to the a.out user.
To enable profiling, the kernel must be rebooted, because no profiling module is available, and it wouldn't be easy to build. To enable profiling, you can specify "profile=2" (or another number) on the kernel commandline. The number you specify is the two-exponent used as profiling step.
/proc/profile A binary snapshot of the profiling buffer. /usr/src/linux/System.map The symbol table for the kernel. /usr/src/linux/* The program being profiled :-)
The readprofile command is part of the util-linux package and is available from Linux Kernel Archive
Tutoriais de Tecnologia Web