Hi Berry, monitoring this kind of activity is typically quite hard. Often enough, the system might lie to you in terms of real activity. Thus here just one short recommendation regarding profiling kernel functions:
Typically what you do is: 1. add profile=2 to the kernel commandline. Double check that it made it there with # cat /proc/cmdline 2. The command to read which functions have been called and how much time they used is readprofile. This command is available from the package util-linux. 3. There is also a reset switch to readprofile to start counting again after boot is completed. If you want to do a temporary boot with the profile=2, you might want to use the following command to boot: # grub2-emu -X note, that -X makes the system really boot, without it would just do as if. This allows to edit within boot configs without having to fiddle with 3215 and emulated Emacs-like control keys. For permanent modification of the command line, have a look at /etc/default/grub (and update grub according to the comments at the top of that file). Berthold ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
