From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Liu, Changcheng" <changcheng.liu@intel.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: refine structure rcu_node field for rcu boost
Date: Thu, 18 Jan 2018 09:38:25 -0800 [thread overview]
Message-ID: <20180118173825.GG9671@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180118103342.GA114176@sofia>
On Thu, Jan 18, 2018 at 06:33:43PM +0800, Liu, Changcheng wrote:
> Do not allocate space for rcu boost field when
> RCU BOOST is not configured.
>
> Signed-off-by: Liu Changcheng <changcheng.liu@intel.com>
The added #ifdef in rcu_read_unlock_special() is a deal-breaker.
Just out of curiosity, is this decrease in storage measurable at
the system level?
Thanx, Paul
> diff --git a/kernel/rcu/tree.h b/kernel/rcu/tree.h
> index 46a5d19..88f087e 100644
> --- a/kernel/rcu/tree.h
> +++ b/kernel/rcu/tree.h
> @@ -129,6 +129,7 @@ struct rcu_node {
> /* if there is no such task. If there */
> /* is no current expedited grace period, */
> /* then there can cannot be any such task. */
> +#ifdef CONFIG_RCU_BOOST
> struct list_head *boost_tasks;
> /* Pointer to first task that needs to be */
> /* priority boosted, or NULL if no priority */
> @@ -153,6 +154,8 @@ struct rcu_node {
> /* Number of tasks boosted for expedited GP. */
> unsigned long n_normal_boosts;
> /* Number of tasks boosted for normal GP. */
> +#endif/* #ifdef CONFIG_RCU_BOOST*/
> +
> #ifdef CONFIG_RCU_NOCB_CPU
> struct swait_queue_head nocb_gp_wq[2];
> /* Place for rcu_nocb_kthread() to wait GP. */
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> index db85ca3..fee0b1e 100644
> --- a/kernel/rcu/tree_plugin.h
> +++ b/kernel/rcu/tree_plugin.h
> @@ -506,8 +506,10 @@ void rcu_read_unlock_special(struct task_struct *t)
> if (IS_ENABLED(CONFIG_RCU_BOOST)) {
> /* Snapshot ->boost_mtx ownership w/rnp->lock held. */
> drop_boost_mutex = rt_mutex_owner(&rnp->boost_mtx) == t;
> +#ifdef CONFIG_RCU_BOOST
> if (&t->rcu_node_entry == rnp->boost_tasks)
> rnp->boost_tasks = np;
> +#endif
> }
>
> /*
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-01-18 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 10:33 Liu, Changcheng
2018-01-18 17:38 ` Paul E. McKenney [this message]
2018-01-19 1:21 ` Liu, Changcheng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180118173825.GG9671@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=changcheng.liu@intel.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome