linux-kernel - Re: workqueue thing

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: <20091223142011.GD4799@sirena.org.uk>
Date:	Wed, 23 Dec 2009 14:20:12 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>, awalls@...ix.net,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	jens.axboe@...cle.com, rusty@...tcorp.com.au,
	cl@...ux-foundation.org, dhowells@...hat.com,
	arjan@...ux.intel.com, avi@...hat.com, johannes@...solutions.net,
	andi@...stfloor.org
Subject: Re: workqueue thing

On Wed, Dec 23, 2009 at 05:25:44AM -0500, Jeff Garzik wrote:
> On 12/23/2009 03:41 AM, Peter Zijlstra wrote:

>> So why are threaded interrupts not considered? Isn't the typical atomic
>> context of drivers the IRQ handler?

> I don't see a whole lot of driver authors rushing to support threaded  
> interrupts.  It is questionable whether the myriad crazy IDE interrupt  

Threaded interrupts are fairly new and there's not an enormous win from
converting existing drivers at present, it's more likely that new code
will use them at the minute.

> routing schemes are even compatible.  Thomas's Mar 23 2009 email says  
> "the primary handler must disable the interrupt at the device level"  
> That is not an easy request for all the hardware libata must support.

That requirement is no longer there since it was making threaded
interrupts useless for devices controlled over interrupt driven buses,
which are one of the major use cases for threaded IRQs.

None of which should be taken as a comment on the proposal under
discusssion.
--
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/