From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
To: rcu@vger.kernel.org
Cc: rushikesh.s.kadam@intel.com, urezki@gmail.com,
neeraj.iitr10@gmail.com, frederic@kernel.org, paulmck@kernel.org,
rostedt@goodmis.org,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: [RFC v1 13/14] rcu/kfree: Fix kfree_rcu_shrink_count() return value
Date: Thu, 12 May 2022 03:04:41 +0000 [thread overview]
Message-ID: <20220512030442.2530552-14-joel@joelfernandes.org> (raw)
In-Reply-To: <20220512030442.2530552-1-joel@joelfernandes.org>
As per the comments in include/linux/shrinker.h, .count_objects callback
should return the number of freeable items, but if there are no objects
to free, SHRINK_EMPTY should be returned. The only time 0 is returned
should be when we are unable to determine the number of objects, or the
cache should be skipped for another reason.
Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
---
kernel/rcu/tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
index 3828ac3bf1c4..f191542cdf5e 100644
--- a/kernel/rcu/tree.c
+++ b/kernel/rcu/tree.c
@@ -3637,7 +3637,7 @@ kfree_rcu_shrink_count(struct shrinker *shrink, struct shrink_control *sc)
atomic_set(&krcp->backoff_page_cache_fill, 1);
}
- return count;
+ return count == 0 ? SHRINK_EMPTY : count;
}
static unsigned long
--
2.36.0.550.gb090851708-goog
next prev parent reply other threads:[~2022-05-12 3:05 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
2022-05-14 19:48 ` Uladzislau Rezki
2022-05-12 3:04 ` Joel Fernandes (Google) [this message]
2022-05-13 14:54 ` [RFC v1 13/14] rcu/kfree: Fix kfree_rcu_shrink_count() return value 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=20220512030442.2530552-14-joel@joelfernandes.org \
--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;
as well as URLs for NNTP newsgroup(s).