linux-kernel - Re: [sched_delayed] sched: RT throttling activated

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1377261222.14021.23.camel@jlt4.sipsolutions.net>
Date:	Fri, 23 Aug 2013 14:33:42 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Martin Mokrejs <mmokrejs@...d.natur.cuni.cz>,
	Theodore Tso <tytso@....edu>,
	Thomas Gleixner <tglx@...utronix.de>, mingo@...hat.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [sched_delayed] sched: RT throttling activated

On Fri, 2013-08-23 at 14:10 +0200, Peter Zijlstra wrote:

> >  2161  FF [irq/50-iwlwifi]
> 
> Oh a threaded interrupt, I presume you're not using "threadiqrs" since
> this is the only interrupt thread around and I see a
> 'request_threaded_irq()' call in
> drivers/net/wireless/iwlwifi/pcie/trans.c
> 
> And wow, why would that thing consume that much cpu. 

How much is "that much"?

> Johill, ever seen the iwlwifi interrupt go 'funny' and consume gobs of
> cpu-time?

Not really, no, though if you do a lot of data transfer it can actually
consume a fair bit of CPU - made better by two somewhat recent patches,
commits 01911dab97cb3e21e640aaca82689acec00ed848 and
68972c46f2975d3d61f9dc9f311f77bfc8a8b12b.

johannes

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