linux-kernel - Re: LTTng finds abnormally long APIC interrupt handler : 58.2 ms

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]

Date:	Sat, 09 Aug 2008 09:14:25 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	ltt-dev@...ts.casi.polymtl.ca
Subject: Re: LTTng finds abnormally long APIC interrupt handler : 58.2 ms

On Fri, 2008-08-08 at 19:11 -0400, Mathieu Desnoyers wrote:

> The basic question that arises from this trace is : is it normal for
> find_usage_backwards to be called ~8500 times during a spinlock ?

Yes and no - its O(n^2) graph walking. That said, David Miller did a
cool patch that reduces the graph walk by not doing the same subgraph
over and over again. Look at this series:

  http://lkml.org/lkml/2008/8/4/175

Andrew picked all that up - so it should be in the next -mm.

It also contains a new scheduler run-queue annotation which should
greatly reduce the chain length, adding to even more benefit.

--
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/