On 30 Apr 1999, Linus Torvalds wrote:
> Note that the easiest way to do spinlock profiling is actually to just
> do a normal "profile" of the kernel, and looking into the ".text_lock"
> part of the profile. That works for spinlocks that don't disable
> interrupts, notably the kernel lock (which is the biggest one by far).
>
> There are various kernel profiling programs out there that just read
> /proc/profile and parse the output. That's what I do, and it's very
> instructive (you can tell not only which spinlock, but _what_invocation_
> of the lock that is the one that gets the worst behaviour).
i'm using "readprofile" right now, but i don't see a .text_lock section in
the profile output. which tool do you prefer?
- Chuck Lever
--
corporate: <[EMAIL PROTECTED]>
personal: <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
The Linux Scalability project:
http://www.citi.umich.edu/projects/linux-scalability/
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
