linux-kernel - [RFC patch 0/5] Per cpu thread hotplug infrastructure

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2012 11:00:53 -0000
From:	Thomas Gleixner <tglx@...utronix.de>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Tejun Heo <tj@...nel.org>
Subject: [RFC patch 0/5] Per cpu thread hotplug infrastructure

The following series implements the infrastructure for parking and
unparking kernel threads to avoid the full teardown and fork on cpu
hotplug operations along with management infrastructure for hotplug
and users.

I've converted the most obvious (and simple) users ksoftirqd and
watchdog along with a driver (the latter is untested due to lack of
hardware).

Looking at the other (ab)users of per cpu kernel threads:

 - drivers/* should be rather trivial to convert all users

 - RCU needs more thought, but I'm sure that Paul will figure it out
   in no time :)

   The main issue with RCU are the per node threads, but it should be
   simple to extend the infrastructure to allow registration and
   handling of per node threads as well.

 - workqueues. I did not even try to think about converting it. The
   hotplug related code in there causes strong feelings related to
   zombies and chainsaws. (See https://lwn.net/Articles/378036/)

Thanks,

	tglx

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