From: Frederic Weisbecker <frederic@kernel.org>
To: Zqiang <qiang1.zhang@intel.com>
Cc: paulmck@kernel.org, joel@joelfernandes.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] srcu: Add detection of boot CPU srcu_data structure's->srcu_cblist
Date: Thu, 17 Nov 2022 15:20:25 +0100 [thread overview]
Message-ID: <20221117142025.GE839309@lothringen> (raw)
In-Reply-To: <20221117112050.3942407-1-qiang1.zhang@intel.com>
On Thu, Nov 17, 2022 at 07:20:50PM +0800, Zqiang wrote:
> Before SRCU_SIZE_WAIT_CALL srcu_size_state is reached, the srcu
> callback only insert to boot-CPU srcu_data structure's->srcu_cblist
> and other CPU srcu_data structure's->srcu_cblist is always empty. so
> before SRCU_SIZE_WAIT_CALL is reached, need to correctly check boot-CPU
> pend cbs in srcu_might_be_idle().
>
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>
> ---
> kernel/rcu/srcutree.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> index 6af031200580..6d9af9901765 100644
> --- a/kernel/rcu/srcutree.c
> +++ b/kernel/rcu/srcutree.c
> @@ -1098,8 +1098,11 @@ static bool srcu_might_be_idle(struct srcu_struct *ssp)
> unsigned long tlast;
>
> check_init_srcu_struct(ssp);
> - /* If the local srcu_data structure has callbacks, not idle. */
> - sdp = raw_cpu_ptr(ssp->sda);
> + /* If the boot CPU or local srcu_data structure has callbacks, not idle. */
> + if (smp_load_acquire(&ssp->srcu_size_state) < SRCU_SIZE_WAIT_CALL)
> + sdp = per_cpu_ptr(ssp->sda, get_boot_cpu_id());
> + else
> + sdp = raw_cpu_ptr(ssp->sda);
While at it if someone is interested in documenting/commenting on the meaning of
all these SRCU_SIZE_* things, it would be much appreciated!
Thanks.
> spin_lock_irqsave_rcu_node(sdp, flags);
> if (rcu_segcblist_pend_cbs(&sdp->srcu_cblist)) {
> spin_unlock_irqrestore_rcu_node(sdp, flags);
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-11-17 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 11:20 Zqiang
2022-11-17 14:20 ` Frederic Weisbecker [this message]
2022-11-18 4:53 ` Zhang, Qiang1
2022-11-23 2:01 ` Zhang, Qiang1
2022-11-23 19:04 ` Paul E. McKenney
2022-11-24 1:43 ` Zhang, Qiang1
2022-11-24 5:25 ` Paul E. McKenney
2022-11-24 5:59 ` Zhang, Qiang1
2022-11-28 8:32 ` Pingfan Liu
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=20221117142025.GE839309@lothringen \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=rcu@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
all inboxes | Powered by JetHome®