linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Neeraj Upadhyay <neeraju@codeaurora.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Stable <stable@vger.kernel.org>,
	Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH 05/16] rcu/nocb: Disable bypass when CPU isn't completely offloaded
Date: Thu, 28 Jan 2021 13:31:33 -0800	[thread overview]
Message-ID: <20210128213133.GT2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20210128171222.131380-6-frederic@kernel.org>

On Thu, Jan 28, 2021 at 06:12:11PM +0100, Frederic Weisbecker wrote:
> Instead of flushing bypass at the very last moment in the deoffloading
> process, just disable bypass enqueue at soon as we start the deoffloading
> process and flush the pending bypass early. It's less fragile and we
> leave some time to the kthreads and softirqs to process quietly.
> 
> Symmetrically, only enable bypass once we safely complete the offloading
> process.
> 
> Reported-by: Paul E. McKenney <paulmck@kernel.org>
> Cc: Josh Triplett <josh@joshtriplett.org>
> Cc: Lai Jiangshan <jiangshanlai@gmail.com>
> Cc: Joel Fernandes <joel@joelfernandes.org>
> Cc: Neeraj Upadhyay <neeraju@codeaurora.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>

Looks plausible, thank you!  Some questions and comments below.

> ---
>  include/linux/rcu_segcblist.h |  7 ++++---
>  kernel/rcu/tree_plugin.h      | 31 +++++++++++++++++++++++--------
>  2 files changed, 27 insertions(+), 11 deletions(-)
> 
> diff --git a/include/linux/rcu_segcblist.h b/include/linux/rcu_segcblist.h
> index 8afe886e85f1..5a2d6dadd720 100644
> --- a/include/linux/rcu_segcblist.h
> +++ b/include/linux/rcu_segcblist.h
> @@ -109,7 +109,7 @@ struct rcu_cblist {
>   *  |                           SEGCBLIST_KTHREAD_GP                           |
>   *  |                                                                          |
>   *  |   Kthreads handle callbacks holding nocb_lock, local rcu_core() stops    |
> - *  |   handling callbacks.                                                    |
> + *  |   handling callbacks. Allow bypass enqueue.                              |

"Allow bypass enqueue" as in bypass was disabled and entering this
state causes it to be enabled, correct?  If so, "Enable bypass
queueing" would be less ambiguous and would match the change below.

>   *  ----------------------------------------------------------------------------
>   */
>  
> @@ -125,7 +125,7 @@ struct rcu_cblist {
>   *  |                           SEGCBLIST_KTHREAD_GP                           |
>   *  |                                                                          |
>   *  |   CB/GP kthreads handle callbacks holding nocb_lock, local rcu_core()    |
> - *  |   ignores callbacks.                                                     |
> + *  |   ignores callbacks. Bypass enqueue is enabled.                          |
>   *  ----------------------------------------------------------------------------
>   *                                      |
>   *                                      v
> @@ -134,7 +134,8 @@ struct rcu_cblist {
>   *  |                           SEGCBLIST_KTHREAD_GP                           |
>   *  |                                                                          |
>   *  |   CB/GP kthreads and local rcu_core() handle callbacks concurrently      |
> - *  |   holding nocb_lock. Wake up CB and GP kthreads if necessary.            |
> + *  |   holding nocb_lock. Wake up CB and GP kthreads if necessary. Disable    |
> + *  |   bypass enqueue.                                                        |
>   *  ----------------------------------------------------------------------------
>   *                                      |
>   *                                      v
> diff --git a/kernel/rcu/tree_plugin.h b/kernel/rcu/tree_plugin.h
> index 732942a15f2b..7781830a3cf1 100644
> --- a/kernel/rcu/tree_plugin.h
> +++ b/kernel/rcu/tree_plugin.h
> @@ -1825,11 +1825,22 @@ static bool rcu_nocb_try_bypass(struct rcu_data *rdp, struct rcu_head *rhp,
>  	unsigned long j = jiffies;
>  	long ncbs = rcu_cblist_n_cbs(&rdp->nocb_bypass);
>  
> +	lockdep_assert_irqs_disabled();
> +
> +	// Pure softirq/rcuc based processing: no bypassing, no
> +	// locking.
>  	if (!rcu_rdp_is_offloaded(rdp)) {
> +		*was_alldone = !rcu_segcblist_pend_cbs(&rdp->cblist);
> +		return false;
> +	}
> +
> +	// In the process of (de-)offloading: no bypassing, but
> +	// locking.
> +	if (!rcu_segcblist_completely_offloaded(&rdp->cblist)) {
> +		rcu_nocb_lock(rdp);
>  		*was_alldone = !rcu_segcblist_pend_cbs(&rdp->cblist);
>  		return false; /* Not offloaded, no bypassing. */
>  	}
> -	lockdep_assert_irqs_disabled();
>  
>  	// Don't use ->nocb_bypass during early boot.
>  	if (rcu_scheduler_active != RCU_SCHEDULER_RUNNING) {
> @@ -2412,6 +2423,7 @@ static long rcu_nocb_rdp_deoffload(void *arg)
>  
>  	rcu_nocb_lock_irqsave(rdp, flags);
>  
> +	WARN_ON_ONCE(!rcu_nocb_flush_bypass(rdp, NULL, jiffies));

This flush suffices because we are running on the target CPU
holding ->nocb_lock (thus having interrupts disabled), and
because rdp_offload_toggle() invokes rcu_segcblist_offload(),
which clears SEGCBLIST_OFFLOADED.  Thus future calls to
rcu_segcblist_completely_offloaded() will return false,
which means that future calls to rcu_nocb_try_bypass() will
refuse to put anything into the bypass.

I believe that this deserves a comment, particularly if I am
confused about what is really happening here.  ;-)

On another topic, since I saw it along the way...

The header comment for rcu_segcblist_offload() says that the
structure must be empty, but that isn't really the case, is it?

>  	ret = rdp_offload_toggle(rdp, false, flags);
>  	swait_event_exclusive(rdp->nocb_state_wq,
>  			      !rcu_segcblist_test_flags(cblist, SEGCBLIST_KTHREAD_CB |
> @@ -2422,19 +2434,22 @@ static long rcu_nocb_rdp_deoffload(void *arg)
>  	rcu_nocb_unlock_irqrestore(rdp, flags);
>  	del_timer_sync(&rdp->nocb_timer);
>  
> +	/* Sanity check */
> +	WARN_ON_ONCE(rcu_cblist_n_cbs(&rdp->nocb_bypass));
> +
>  	/*
> -	 * Flush bypass. While IRQs are disabled and once we set
> -	 * SEGCBLIST_SOFTIRQ_ONLY, no callback is supposed to be
> -	 * enqueued on bypass.
> +	 * Lock one last time so we see latest updates from kthreads and timer

You lost me here.  What updates are we seeing from kthreads and timers?

> +	 * so that we can later run callbacks locally without the lock.
>  	 */
>  	rcu_nocb_lock_irqsave(rdp, flags);
> -	rcu_nocb_flush_bypass(rdp, NULL, jiffies);
> +	/*
> +	 * Theoretically we could set SEGCBLIST_SOFTIRQ_ONLY after the nocb
> +	 * LOCK/UNLOCK but let's be paranoid.
> +	 */
>  	rcu_segcblist_set_flags(cblist, SEGCBLIST_SOFTIRQ_ONLY);

As long as we are being paranoid, should we also check that the
bypass remains empty?

>  	/*
>  	 * With SEGCBLIST_SOFTIRQ_ONLY, we can't use
> -	 * rcu_nocb_unlock_irqrestore() anymore. Theoretically we
> -	 * could set SEGCBLIST_SOFTIRQ_ONLY with cb unlocked and IRQs
> -	 * disabled now, but let's be paranoid.
> +	 * rcu_nocb_unlock_irqrestore() anymore.
>  	 */
>  	raw_spin_unlock_irqrestore(&rdp->nocb_lock, flags);
>  
> -- 
> 2.25.1
> 

  reply	other threads:[~2021-01-28 21:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 17:12 [PATCH 00/16] rcu/nocb updates Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 01/16] rcu/nocb: Fix potential missed nocb_timer rearm Frederic Weisbecker
     [not found]   ` <20210128184834.GP2743@paulmck-ThinkPad-P72>
2021-01-28 21:23     ` Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 02/16] rcu/nocb: Comment the reason behind BH disablement on batch processing Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 03/16] rcu/nocb: Forbid NOCB toggling on offline CPUs Frederic Weisbecker
2021-01-28 19:52   ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 04/16] rcu/nocb: Only (re-)initialize segcblist when needed on CPU up Frederic Weisbecker
     [not found]   ` <20210128191228.GQ2743@paulmck-ThinkPad-P72>
2021-01-28 21:34     ` Frederic Weisbecker
2021-01-28 21:45       ` Paul E. McKenney
2021-01-29  0:26         ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 05/16] rcu/nocb: Disable bypass when CPU isn't completely offloaded Frederic Weisbecker
2021-01-28 21:31   ` Paul E. McKenney [this message]
2021-01-28 22:25     ` Frederic Weisbecker
2021-01-29  0:19       ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 06/16] rcu/nocb: Avoid confusing double write of rdp->nocb_cb_sleep Frederic Weisbecker
2021-01-28 21:42   ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 07/16] rcu/nocb: Rename nocb_gp_update_state to nocb_gp_update_state_deoffloading Frederic Weisbecker
2021-01-29  0:49   ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 08/16] rcu/nocb: Move trace_rcu_nocb_wake() calls outside nocb_lock when possible Frederic Weisbecker
2021-01-29  0:51   ` Paul E. McKenney
2021-01-28 17:12 ` [PATCH 09/16] rcu/nocb: Merge nocb_timer to the rdp leader Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 10/16] rcu/nocb: Directly call __wake_nocb_gp() from bypass timer Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 11/16] rcu/nocb: Allow de-offloading rdp leader Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 12/16] rcu/nocb: Cancel nocb_timer upon nocb_gp wakeup Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 13/16] rcu/nocb: Delete bypass_timer " Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 14/16] rcu/nocb: Only cancel nocb timer if not polling Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 15/16] rcu/nocb: Prepare for finegrained deferred wakeup Frederic Weisbecker
2021-01-28 17:12 ` [PATCH 16/16] rcu/nocb: Unify timers Frederic Weisbecker

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=20210128213133.GT2743@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neeraju@codeaurora.org \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).