linux-kernel - Re: [RFC][PATCH] create workqueue threads only when needed

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]

Date:	Mon, 2 Feb 2009 10:14:07 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC][PATCH] create workqueue threads only when needed

Am Monday 02 February 2009 10:05:28 schrieb Benjamin Herrenschmidt:
> > Work which /may/ sleep longer, for example performs SCSI transactions,
> > needs to go into a private workqueue or other kind of context.
> 
> Well, it's a bit silly to allocate a private workqueue with all it's
> associated per CPU kernel threads for something as rare as resetting
> your eth NIC ... or even SCSI error handling in fact.

How do you avoid a deadlock if SCSI error handling doesn't use
a dedicated workqueue?

	Regards
		Oliver

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