Re: do_raw_spin_lock using a lot of the system cpu time

[David Ahern]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/