From: Joel Fernandes <joel@joelfernandes.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: rcu@vger.kernel.org, rushikesh.s.kadam@intel.com,
neeraj.iitr10@gmail.com, frederic@kernel.org, paulmck@kernel.org,
rostedt@goodmis.org
Subject: Re: [RFC v1 12/14] rcu/kfree: remove useless monitor_todo flag
Date: Sat, 14 May 2022 14:35:24 +0000 [thread overview]
Message-ID: <Yn++LOrXH615Q1DU@google.com> (raw)
In-Reply-To: <Yn5w0fOga4mEHEAt@pc638.lan>
On Fri, May 13, 2022 at 04:53:05PM +0200, Uladzislau Rezki wrote:
> > monitor_todo is not needed as the work struct already tracks if work is
> > pending. Just use that to know if work is pending using
> > delayed_work_pending() helper.
> >
> > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > ---
> > kernel/rcu/tree.c | 22 +++++++---------------
> > 1 file changed, 7 insertions(+), 15 deletions(-)
> >
> > diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> > index 3baf29014f86..3828ac3bf1c4 100644
> > --- a/kernel/rcu/tree.c
> > +++ b/kernel/rcu/tree.c
> > @@ -3155,7 +3155,6 @@ struct kfree_rcu_cpu_work {
> > * @krw_arr: Array of batches of kfree_rcu() objects waiting for a grace period
> > * @lock: Synchronize access to this structure
> > * @monitor_work: Promote @head to @head_free after KFREE_DRAIN_JIFFIES
> > - * @monitor_todo: Tracks whether a @monitor_work delayed work is pending
> > * @initialized: The @rcu_work fields have been initialized
> > * @count: Number of objects for which GP not started
> > * @bkvcache:
> > @@ -3180,7 +3179,6 @@ struct kfree_rcu_cpu {
> > struct kfree_rcu_cpu_work krw_arr[KFREE_N_BATCHES];
> > raw_spinlock_t lock;
> > struct delayed_work monitor_work;
> > - bool monitor_todo;
> > bool initialized;
> > int count;
> >
> > @@ -3416,9 +3414,7 @@ static void kfree_rcu_monitor(struct work_struct *work)
> > // of the channels that is still busy we should rearm the
> > // work to repeat an attempt. Because previous batches are
> > // still in progress.
> > - if (!krcp->bkvhead[0] && !krcp->bkvhead[1] && !krcp->head)
> > - krcp->monitor_todo = false;
> > - else
> > + if (krcp->bkvhead[0] || krcp->bkvhead[1] || krcp->head)
> > schedule_delayed_work(&krcp->monitor_work, KFREE_DRAIN_JIFFIES);
> >
> > raw_spin_unlock_irqrestore(&krcp->lock, flags);
> > @@ -3607,10 +3603,8 @@ void kvfree_call_rcu(struct rcu_head *head, rcu_callback_t func)
> >
> > // Set timer to drain after KFREE_DRAIN_JIFFIES.
> > if (rcu_scheduler_active == RCU_SCHEDULER_RUNNING &&
> > - !krcp->monitor_todo) {
> > - krcp->monitor_todo = true;
> > + !delayed_work_pending(&krcp->monitor_work))
> > schedule_delayed_work(&krcp->monitor_work, KFREE_DRAIN_JIFFIES);
> > - }
> >
> > unlock_return:
> > krc_this_cpu_unlock(krcp, flags);
> > @@ -3685,14 +3679,12 @@ void __init kfree_rcu_scheduler_running(void)
> > struct kfree_rcu_cpu *krcp = per_cpu_ptr(&krc, cpu);
> >
> > raw_spin_lock_irqsave(&krcp->lock, flags);
> > - if ((!krcp->bkvhead[0] && !krcp->bkvhead[1] && !krcp->head) ||
> > - krcp->monitor_todo) {
> > - raw_spin_unlock_irqrestore(&krcp->lock, flags);
> > - continue;
> > + if (krcp->bkvhead[0] || krcp->bkvhead[1] || krcp->head) {
> > + if (delayed_work_pending(&krcp->monitor_work)) {
> > + schedule_delayed_work_on(cpu, &krcp->monitor_work,
> > + KFREE_DRAIN_JIFFIES);
> > + }
> > }
> > - krcp->monitor_todo = true;
> > - schedule_delayed_work_on(cpu, &krcp->monitor_work,
> > - KFREE_DRAIN_JIFFIES);
> > raw_spin_unlock_irqrestore(&krcp->lock, flags);
> > }
> > }
> > --
> >
> Looks good to me from the first glance, but let me know to have a look
> at it more closely.
Thanks, I appreciate it.
- Joel
next prev parent reply other threads:[~2022-05-14 14:35 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 3:04 [RFC v1 00/14] Implement call_rcu_lazy() and miscellaneous fixes Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 01/14] rcu: Add a lock-less lazy RCU implementation Joel Fernandes (Google)
2022-05-12 23:56 ` Paul E. McKenney
2022-05-14 15:08 ` Joel Fernandes
2022-05-14 16:34 ` Paul E. McKenney
2022-05-27 23:12 ` Joel Fernandes
2022-05-28 17:57 ` Paul E. McKenney
2022-05-30 14:48 ` Joel Fernandes
2022-05-30 16:42 ` Paul E. McKenney
2022-05-31 2:12 ` Joel Fernandes
2022-05-31 4:26 ` Paul E. McKenney
2022-05-31 16:11 ` Joel Fernandes
2022-05-31 16:45 ` Paul E. McKenney
2022-05-31 18:51 ` Joel Fernandes
2022-05-31 19:25 ` Paul E. McKenney
2022-05-31 21:29 ` Joel Fernandes
2022-05-31 22:44 ` Joel Fernandes
2022-06-01 14:24 ` Frederic Weisbecker
2022-06-01 16:17 ` Paul E. McKenney
2022-06-01 19:09 ` Joel Fernandes
2022-05-17 9:07 ` Uladzislau Rezki
2022-05-30 14:54 ` Joel Fernandes
2022-06-01 14:12 ` Frederic Weisbecker
2022-06-01 19:10 ` Joel Fernandes
2022-05-12 3:04 ` [RFC v1 02/14] workqueue: Add a lazy version of queue_rcu_work() Joel Fernandes (Google)
2022-05-12 23:58 ` Paul E. McKenney
2022-05-14 14:44 ` Joel Fernandes
2022-05-12 3:04 ` [RFC v1 03/14] block/blk-ioc: Move call_rcu() to call_rcu_lazy() Joel Fernandes (Google)
2022-05-13 0:00 ` Paul E. McKenney
2022-05-12 3:04 ` [RFC v1 04/14] cred: " Joel Fernandes (Google)
2022-05-13 0:02 ` Paul E. McKenney
2022-05-14 14:41 ` Joel Fernandes
2022-05-12 3:04 ` [RFC v1 05/14] fs: Move call_rcu() to call_rcu_lazy() in some paths Joel Fernandes (Google)
2022-05-13 0:07 ` Paul E. McKenney
2022-05-14 14:40 ` Joel Fernandes
2022-05-12 3:04 ` [RFC v1 06/14] kernel: Move various core kernel usages to call_rcu_lazy() Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 07/14] security: Move call_rcu() " Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 08/14] net/core: " Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 09/14] lib: " Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 10/14] kfree/rcu: Queue RCU work via queue_rcu_work_lazy() Joel Fernandes (Google)
2022-05-13 0:12 ` Paul E. McKenney
2022-05-13 14:55 ` Uladzislau Rezki
2022-05-14 14:33 ` Joel Fernandes
2022-05-14 19:10 ` Uladzislau Rezki
2022-05-12 3:04 ` [RFC v1 11/14] i915: Move call_rcu() to call_rcu_lazy() Joel Fernandes (Google)
2022-05-12 3:04 ` [RFC v1 12/14] rcu/kfree: remove useless monitor_todo flag Joel Fernandes (Google)
2022-05-13 14:53 ` Uladzislau Rezki
2022-05-14 14:35 ` Joel Fernandes [this message]
2022-05-14 19:48 ` Uladzislau Rezki
2022-05-12 3:04 ` [RFC v1 13/14] rcu/kfree: Fix kfree_rcu_shrink_count() return value Joel Fernandes (Google)
2022-05-13 14:54 ` Uladzislau Rezki
2022-05-14 14:34 ` Joel Fernandes
2022-05-12 3:04 ` [RFC v1 14/14] DEBUG: Toggle rcu_lazy and tune at runtime Joel Fernandes (Google)
2022-05-13 0:16 ` Paul E. McKenney
2022-05-14 14:38 ` Joel Fernandes
2022-05-14 16:21 ` Paul E. McKenney
2022-05-12 3:17 ` [RFC v1 00/14] Implement call_rcu_lazy() and miscellaneous fixes Joel Fernandes
2022-05-12 13:09 ` Uladzislau Rezki
2022-05-12 13:56 ` Uladzislau Rezki
2022-05-12 14:03 ` Joel Fernandes
2022-05-12 14:37 ` Uladzislau Rezki
2022-05-12 16:09 ` Joel Fernandes
2022-05-12 16:32 ` Uladzislau Rezki
[not found] ` <Yn5e7w8NWzThUARb@pc638.lan>
2022-05-13 14:51 ` Joel Fernandes
2022-05-13 15:43 ` Uladzislau Rezki
2022-05-14 14:25 ` Joel Fernandes
2022-05-14 19:01 ` Uladzislau Rezki
2022-08-09 2:25 ` Joel Fernandes
2022-05-13 0:23 ` Paul E. McKenney
2022-05-13 14:45 ` Joel Fernandes
2022-06-13 18:53 ` Joel Fernandes
2022-06-13 22:48 ` Paul E. McKenney
2022-06-16 16:26 ` Joel Fernandes
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=Yn++LOrXH615Q1DU@google.com \
--to=joel@joelfernandes.org \
--cc=frederic@kernel.org \
--cc=neeraj.iitr10@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rushikesh.s.kadam@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox