linux-kernel - Re: do_raw_spin_lock using a lot of the system cpu time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4D50D2B0.8030106@gmail.com>
Date:	Mon, 07 Feb 2011 22:20:48 -0700
From:	David Ahern <dsahern@...il.com>
To:	"J.H." <warthog9@...nel.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	"hpa@...nel.org" <hpa@...nel.org>, dgc@...nel.org,
	elder@...nel.org, hch@...nel.org
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/