linux-kernel - Re: [PATCH] rcu: unify boost and kthread priorities

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: <1410972543.31130.87.camel@x220>
Date:	Wed, 17 Sep 2014 18:49:03 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Clark Williams <clark.williams@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rcu: unify boost and kthread priorities

Hi Paul,

On Tue, 2014-09-16 at 13:41 -0700, Paul E. McKenney wrote:
> rcu: unify boost and kthread priorities
> 
> Rename CONFIG_RCU_BOOST_PRIO to CONFIG_RCU_KTHREAD_PRIO and use this
> value for both the per-CPU kthreads (rcuc/N) and the rcu boosting
> threads (rcub/n).
> 
> Also, create the module_parameter rcutree.kthread_prio to be used on
> the kernel command line at boot to set a new value (rcutree.kthread_prio=N).
> 
> Signed-off-by: Clark Williams <clark.williams@...il.com>
> [ paulmck: Ported to rcu/dev. ]
> Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>

This landed in today's linux-next (ie, next-20140917) as commit
04a96e05bda6 ("rcu: unify boost and kthread priorities").

> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>[...]
> diff --git a/init/Kconfig b/init/Kconfig
>[...]
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
>[...]

There's a reference to CONFIG_RCU_BOOST_PRIO in
tools/testing/selftests/rcutorture/doc/TREE_RCU-kconfig.txt. It needs
updating too, doesn't it?


Paul Bolle

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