Linux RCU subsystem development
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Ziwei Dai <ziwei.dai@unisoc.com>
Cc: paulmck@kernel.org, frederic@kernel.org,
	quic_neeraju@quicinc.com, josh@joshtriplett.org,
	rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
	jiangshanlai@gmail.com, joel@joelfernandes.org,
	rcu@vger.kernel.org, shuang.wang@unisoc.com,
	yifan.xin@unisoc.com, ke.wang@unisoc.com, xuewen.yan@unisoc.com,
	zhiguo.niu@unisoc.com
Subject: Re: [PATCH] rcu: Make sure new krcp free business is handled after the wanted rcu grace period.
Date: Thu, 30 Mar 2023 10:52:18 +0200	[thread overview]
Message-ID: <ZCVNwvhJ10iBN+wp@pc636> (raw)
In-Reply-To: <1680161497-19817-1-git-send-email-ziwei.dai@unisoc.com>

On Thu, Mar 30, 2023 at 03:31:37PM +0800, Ziwei Dai wrote:
> From: 代子为 (Ziwei Dai) <ziwei.dai@ziwei-lenovo.spreadtrum.com>
> 
> In kfree_rcu_monitor(), new free business at krcp is attached to any free
> channel at krwp. kfree_rcu_monitor() is responsible to make sure new free
> business is handled after the rcu grace period. But if there is any none-free
> channel at krwp already, that means there is an on-going rcu work,
> which will cause the kvfree_call_rcu()-triggered free business is done
> before the wanted rcu grace period ends.
> 
Right. There have to be a "Fixes:" tag.

> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 8e880c0..4fe3c53 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -3107,15 +3107,16 @@ static void kfree_rcu_monitor(struct work_struct *work)
>         for (i = 0; i < KFREE_N_BATCHES; i++) {
>                 struct kfree_rcu_cpu_work *krwp = &(krcp->krw_arr[i]);
> 
> -               // Try to detach bulk_head or head and attach it over any
> -               // available corresponding free channel. It can be that
> -               // a previous RCU batch is in progress, it means that
> -               // immediately to queue another one is not possible so
> -               // in that case the monitor work is rearmed.
> -               if ((!list_empty(&krcp->bulk_head[0]) && list_empty(&krwp->bulk_head_free[0])) ||
> -                       (!list_empty(&krcp->bulk_head[1]) && list_empty(&krwp->bulk_head_free[1])) ||
> -                               (READ_ONCE(krcp->head) && !krwp->head_free)) {
> -
> +               // Try to detach bulk_head or head and attach it, only when
> +               // all channels are free.  Any channel is not free means at krwp
> +               // there is on-going rcu work to handle krwp's free business.
> +               if (!list_empty(&krwp->bulk_head_free[0]) ||
> +                       !list_empty(&krwp->bulk_head_free[1]) ||
> +                               !krwp->head_free)
> +                       continue;
> +               if (!list_empty(&krcp->bulk_head[0]) ||
> +                       !list_empty(&krcp->bulk_head[1]) ||
> +                       READ_ONCE(krcp->head)) {
>                         // Channel 1 corresponds to the SLAB-pointer bulk path.
>                         // Channel 2 corresponds to vmalloc-pointer bulk path.
>                         for (j = 0; j < FREE_N_CHANNELS; j++) {
> --
> 1.9.1
> 
Give me some time to have a look at your change closer. It seems it can
trigger a rcu_work even though krcp is empty. But it is from a first
glance.

Thanks!

--
Uladzislau Rezki

  reply	other threads:[~2023-03-30  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  7:31 [PATCH] rcu: Make sure new krcp free business is handled after the wanted rcu grace period Ziwei Dai
2023-03-30  8:52 ` Uladzislau Rezki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-30  9:21 Ziwei Dai
2023-03-30  9:27 Ziwei Dai

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=ZCVNwvhJ10iBN+wp@pc636 \
    --to=urezki@gmail.com \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=ke.wang@unisoc.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@kernel.org \
    --cc=quic_neeraju@quicinc.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuang.wang@unisoc.com \
    --cc=xuewen.yan@unisoc.com \
    --cc=yifan.xin@unisoc.com \
    --cc=zhiguo.niu@unisoc.com \
    --cc=ziwei.dai@unisoc.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