linux-kernel - Re: + work_on_cpu-rewrite-it-to-create-a-kernel-thread-on-demand.patch added to -mm tree

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: <20090212142314.9ab6ad6f.akpm@linux-foundation.org>
Date:	Thu, 12 Feb 2009 14:23:14 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	ebiederm@...ssion.com (Eric W. Biederman)
Cc:	fweisbec@...il.com, mingo@...e.hu, linux-kernel@...r.kernel.org,
	oleg@...hat.com, travis@....com, a.p.zijlstra@...llo.nl,
	rusty@...tcorp.com.au
Subject: Re: +
 work_on_cpu-rewrite-it-to-create-a-kernel-thread-on-demand.patch  added to
 -mm tree

On Thu, 12 Feb 2009 14:13:06 -0800
ebiederm@...ssion.com (Eric W. Biederman) wrote:

> 
> I should follow up and say that the reason I care right now, is I am
> digging into pci hotplug.  One of the issues I'm fighting is that
> currently I appear to need a dedicated kernel thread for each pci
> hotplug slot.  It gets easy to deadlock the kernel hotplugging
> a hotplug controller otherwise.
> 

um, ok, if you say so...

I'd have thought that a short-lived kernel thread would be appropriate,
if poss.  Physical hotplug of a PCI device isn't a high-frequency
operation.

The new-fangled work_on_cpu() could do that, or maybe the new-fangled
kernel/async.c code.

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