From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, josh@joshtriplett.org,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com,
bobby prani <bobby.prani@gmail.com>
Subject: Re: [PATCH tip/core/rcu 6/7] rcu: Move early-boot callbacks to no-CBs lists for no-CBs CPUs
Date: Tue, 3 Mar 2015 16:57:16 +0000 (UTC) [thread overview]
Message-ID: <1395157403.208223.1425401836167.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1425401148-7848-6-git-send-email-paulmck@linux.vnet.ibm.com>
----- Original Message -----
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> To: linux-kernel@vger.kernel.org
> Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, "mathieu desnoyers"
> <mathieu.desnoyers@efficios.com>, josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
> rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, fweisbec@gmail.com,
> oleg@redhat.com, "bobby prani" <bobby.prani@gmail.com>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> Sent: Tuesday, March 3, 2015 11:45:47 AM
> Subject: [PATCH tip/core/rcu 6/7] rcu: Move early-boot callbacks to no-CBs lists for no-CBs CPUs
>
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
>
> When a CPU is first determined to be a no-CBs CPUs, this commit causes
> any early boot callbacks to be moved to the no-CBs callback list,
> allowing them t obe invoked.
^^^^^
out-of-order space ;)
Thanks,
Mathieu
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> kernel/rcu/tree.c | 1 +
> kernel/rcu/tree_plugin.h | 24 ++++++++++++------------
> 2 files changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 92fd3eab5823..0317bf7d997f 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -2851,6 +2851,7 @@ __call_rcu(struct rcu_head *head, void (*func)(struct
> rcu_head *rcu),
> * and then drop through to queue the callback.
> */
> BUG_ON(cpu != -1);
> + WARN_ON_ONCE(!rcu_is_watching());
> if (!likely(rdp->nxtlist))
> init_default_callback_list(rdp);
> }
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> index 75d5f096bcb0..afddd5641bea 100644
> --- a/kernel/rcu/tree_plugin.h
> +++ b/kernel/rcu/tree_plugin.h
> @@ -2393,18 +2393,8 @@ void __init rcu_init_nohz(void)
> pr_info("\tPoll for callbacks from no-CBs CPUs.\n");
>
> for_each_rcu_flavor(rsp) {
> - for_each_cpu(cpu, rcu_nocb_mask) {
> - struct rcu_data *rdp = per_cpu_ptr(rsp->rda, cpu);
> -
> - /*
> - * If there are early callbacks, they will need
> - * to be moved to the nocb lists.
> - */
> - WARN_ON_ONCE(rdp->nxttail[RCU_NEXT_TAIL] !=
> - &rdp->nxtlist &&
> - rdp->nxttail[RCU_NEXT_TAIL] != NULL);
> - init_nocb_callback_list(rdp);
> - }
> + for_each_cpu(cpu, rcu_nocb_mask)
> + init_nocb_callback_list(per_cpu_ptr(rsp->rda, cpu));
> rcu_organize_nocb_kthreads(rsp);
> }
> }
> @@ -2541,6 +2531,16 @@ static bool init_nocb_callback_list(struct rcu_data
> *rdp)
> if (!rcu_is_nocb_cpu(rdp->cpu))
> return false;
>
> + /* If there are early-boot callbacks, move them to nocb lists. */
> + if (rdp->nxtlist) {
> + rdp->nocb_head = rdp->nxtlist;
> + rdp->nocb_tail = rdp->nxttail[RCU_NEXT_TAIL];
> + atomic_long_set(&rdp->nocb_q_count, rdp->qlen);
> + atomic_long_set(&rdp->nocb_q_count_lazy, rdp->qlen_lazy);
> + rdp->nxtlist = NULL;
> + rdp->qlen = 0;
> + rdp->qlen_lazy = 0;
> + }
> rdp->nxttail[RCU_NEXT_TAIL] = NULL;
> return true;
> }
> --
> 1.8.1.5
>
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-03-03 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:45 [PATCH tip/core/rcu 0/7] Early-boot RCU callbacks for v4.1 Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 1/7] rcu: Abstract default callback-list initialization from init_callback_list() Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 2/7] rcu: Wire ->rda pointers at compile time Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 3/7] rcu: Prevent early-boot RCU callbacks from splatting Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 4/7] rcu: Refine diagnostics for lacking kthread for no-CBs callbacks Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 5/7] rcu: Avoid clobbering early boot callbacks Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 6/7] rcu: Move early-boot callbacks to no-CBs lists for no-CBs CPUs Paul E. McKenney
2015-03-03 16:57 ` Mathieu Desnoyers [this message]
2015-03-03 17:12 ` Paul E. McKenney
2015-03-03 16:45 ` [PATCH tip/core/rcu 7/7] rcu: Move early boot callback tests earlier Paul E. McKenney
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=1395157403.208223.1425401836167.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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