Messages in this thread | | | Date | Mon, 07 Feb 2011 22:20:48 -0700 | From | David Ahern <> | Subject | Re: do_raw_spin_lock using a lot of the system cpu time |
| |
On 02/07/11 17:18, J.H. wrote:
> The debugging that so far is (via perf top) claims that alloc_vmap_area, > rb_next and do_raw_spin_lock are involved in some combination, with > do_raw_spin_lock being the item taking up 80-90% of the time that perf > top can see.
Have you tried 'perf record -ga' to see the various paths to _raw_spin_lock and rb_next?
David
| |