[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180125061815.GV3741@linux.vnet.ibm.com>
Date: Wed, 24 Jan 2018 22:18:15 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: lianglihao@...wei.com
Cc: guohanjun@...wei.com, heng.z@...wei.com, hb.chen@...wei.com,
lihao.liang@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 06/16] rcuperf: Set gp_exp to true for tests to run
On Tue, Jan 23, 2018 at 03:59:31PM +0800, lianglihao@...wei.com wrote:
> From: Lihao Liang <lianglihao@...wei.com>
>
> Signed-off-by: Lihao Liang <lianglihao@...wei.com>
> ---
> kernel/rcu/rcuperf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/rcuperf.c b/kernel/rcu/rcuperf.c
> index ea80fa3e..baccc123 100644
> --- a/kernel/rcu/rcuperf.c
> +++ b/kernel/rcu/rcuperf.c
> @@ -60,7 +60,7 @@ MODULE_AUTHOR("Paul E. McKenney <paulmck@...ux.vnet.ibm.com>");
> #define VERBOSE_PERFOUT_ERRSTRING(s) \
> do { if (verbose) pr_alert("%s" PERF_FLAG "!!! %s\n", perf_type, s); } while (0)
>
> -torture_param(bool, gp_exp, false, "Use expedited GP wait primitives");
> +torture_param(bool, gp_exp, true, "Use expedited GP wait primitives");
This is fine as a convenience for internal testing, but the usual way
to make this happen is using the rcuperf.gp_exp kernel boot parameter.
Or was that not working for you?
Thanx, Paul
> torture_param(int, holdoff, 10, "Holdoff time before test start (s)");
> torture_param(int, nreaders, -1, "Number of RCU reader threads");
> torture_param(int, nwriters, -1, "Number of RCU updater threads");
> --
> 2.14.1.729.g59c0ea183
>
Powered by blists - more mailing lists