linux-kernel - [PATCH tip/core/rcu 0/2] Callback-offloading changes for 3.17

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

Date:	Mon, 7 Jul 2014 15:48:41 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
	peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com,
	edumazet@...gle.com, dvhart@...ux.intel.com, fweisbec@...il.com,
	oleg@...hat.com, sbw@....edu
Subject: [PATCH tip/core/rcu 0/2] Callback-offloading changes for 3.17

Hello!

This series provides a couple of callback-offloading changes:

1.	Parallelize and economize NOCB kthread wakeups to better handle
	cases where callback offloading is used on workloads that have
	many context switches and thus many grace periods.

2.	Don't offload callbacks for a given CPU unless it has been
	explicitly requested for that CPU, either directly at build
	time or boot time, or indirectly at boot time due to that
	CPU being a nohz_full CPU.

							Thanx, Paul

------------------------------------------------------------------------

 b/Documentation/kernel-parameters.txt |    7 
 b/init/Kconfig                        |    4 
 b/kernel/rcu/tree.h                   |   28 +++
 b/kernel/rcu/tree_plugin.h            |  255 ++++++++++++++++++++++++++++------
 4 files changed, 249 insertions(+), 45 deletions(-)

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