From: Boqun Feng <boqun.feng@gmail.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
Neeraj Upadhyay <neeraj.upadhyay@amd.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>, rcu <rcu@vger.kernel.org>
Subject: Re: [PATCH 1/3] rcu/nocb: Use switch/case on NOCB timer state machine
Date: Thu, 10 Oct 2024 01:16:41 -0700 [thread overview]
Message-ID: <ZweNaSTMQOqXRIIN@boqun-archlinux> (raw)
In-Reply-To: <20241002145738.38226-2-frederic@kernel.org>
On Wed, Oct 02, 2024 at 04:57:36PM +0200, Frederic Weisbecker wrote:
> It's more convenient to benefit from the fallthrough feature of
> switch / case to handle the timer state machine. Also a new state is
> about to be added that will take advantage of it.
>
> No intended functional change.
>
> Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> ---
> kernel/rcu/tree_nocb.h | 33 +++++++++++++++++++++++----------
> 1 file changed, 23 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/rcu/tree_nocb.h b/kernel/rcu/tree_nocb.h
> index 97b99cd06923..2fb803f863da 100644
> --- a/kernel/rcu/tree_nocb.h
> +++ b/kernel/rcu/tree_nocb.h
> @@ -271,22 +271,35 @@ static void wake_nocb_gp_defer(struct rcu_data *rdp, int waketype,
>
> raw_spin_lock_irqsave(&rdp_gp->nocb_gp_lock, flags);
>
> - /*
> - * Bypass wakeup overrides previous deferments. In case of
> - * callback storms, no need to wake up too early.
> - */
> - if (waketype == RCU_NOCB_WAKE_LAZY &&
> - rdp->nocb_defer_wakeup == RCU_NOCB_WAKE_NOT) {
In the old code, if this "if" branch is not taken,
> - mod_timer(&rdp_gp->nocb_timer, jiffies + rcu_get_jiffies_lazy_flush());
> - WRITE_ONCE(rdp_gp->nocb_defer_wakeup, waketype);
> - } else if (waketype == RCU_NOCB_WAKE_BYPASS) {
> + switch (waketype) {
> + case RCU_NOCB_WAKE_BYPASS:
> + /*
> + * Bypass wakeup overrides previous deferments. In case of
> + * callback storms, no need to wake up too early.
> + */
> mod_timer(&rdp_gp->nocb_timer, jiffies + 2);
> WRITE_ONCE(rdp_gp->nocb_defer_wakeup, waketype);
> - } else {
... it will end up in this else branch, however,
> + break;
> + case RCU_NOCB_WAKE_LAZY:
> + if (rdp->nocb_defer_wakeup == RCU_NOCB_WAKE_NOT) {
> + mod_timer(&rdp_gp->nocb_timer, jiffies + rcu_get_jiffies_lazy_flush());
> + WRITE_ONCE(rdp_gp->nocb_defer_wakeup, waketype);
> + }
> + /*
> + * If the timer is already armed, a non-lazy enqueue may have happened
> + * in-between. Don't delay it and fall-through.
> + */
> + break;
... here we break instead of fallthrough when waketype ==
RCU_NOCB_WAKE_LAZY and rdp->nocb_defer_wakeup != RCU_NOCB_WAKE_NOT, this
seems to me a functional change, is this intented?
Regards,
Boqun
> + case RCU_NOCB_WAKE:
> + fallthrough;
> + case RCU_NOCB_WAKE_FORCE:
> if (rdp_gp->nocb_defer_wakeup < RCU_NOCB_WAKE)
> mod_timer(&rdp_gp->nocb_timer, jiffies + 1);
> if (rdp_gp->nocb_defer_wakeup < waketype)
> WRITE_ONCE(rdp_gp->nocb_defer_wakeup, waketype);
> + break;
> + default:
> + WARN_ON_ONCE(1);
> }
>
> raw_spin_unlock_irqrestore(&rdp_gp->nocb_gp_lock, flags);
> --
> 2.46.0
>
next prev parent reply other threads:[~2024-10-10 8:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 14:57 [PATCH 0/3] rcu: Fix yet another wake up from offline related issue Frederic Weisbecker
2024-10-02 14:57 ` [PATCH 1/3] rcu/nocb: Use switch/case on NOCB timer state machine Frederic Weisbecker
2024-10-10 8:16 ` Boqun Feng [this message]
2024-10-10 12:55 ` Frederic Weisbecker
2024-10-02 14:57 ` [PATCH 2/3] rcu/nocb: Fix rcuog wake-up from offline softirq Frederic Weisbecker
2024-10-09 18:23 ` Joel Fernandes
2024-10-09 20:56 ` Frederic Weisbecker
2024-10-10 0:27 ` Joel Fernandes
2024-10-02 14:57 ` [PATCH 3/3] rcu: Report callbacks enqueued on offline CPU blind spot Frederic Weisbecker
2024-10-02 15:00 ` Frederic Weisbecker
2024-10-09 2:03 ` Paul E. McKenney
2024-10-09 15:13 ` Paul E. McKenney
2024-10-10 14:30 ` Joel Fernandes
2024-10-09 2:24 ` Neeraj Upadhyay
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=ZweNaSTMQOqXRIIN@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@amd.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.