From: Rafael Aquini <aquini@redhat.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>
Cc: akpm@linux-foundation.org, tkhai@ya.ru, hannes@cmpxchg.org,
shakeelb@google.com, mhocko@kernel.org, roman.gushchin@linux.dev,
muchun.song@linux.dev, david@redhat.com, shy828301@gmail.com,
sultan@kerneltoast.com, dave@stgolabs.net,
penguin-kernel@i-love.sakura.ne.jp, paulmck@kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/7] mm: vmscan: make global slab shrink lockless
Date: Thu, 23 Feb 2023 10:37:21 -0500 [thread overview]
Message-ID: <Y/eIMXtEJVszprNb@optiplex-fbsd> (raw)
In-Reply-To: <Y/eFtTO+8kXlsW7x@optiplex-fbsd>
On Thu, Feb 23, 2023 at 10:26:45AM -0500, Rafael Aquini wrote:
> On Thu, Feb 23, 2023 at 09:27:20PM +0800, Qi Zheng wrote:
> > The shrinker_rwsem is a global lock in shrinkers subsystem,
> > it is easy to cause blocking in the following cases:
> >
> > a. the write lock of shrinker_rwsem was held for too long.
> > For example, there are many memcgs in the system, which
> > causes some paths to hold locks and traverse it for too
> > long. (e.g. expand_shrinker_info())
> > b. the read lock of shrinker_rwsem was held for too long,
> > and a writer came at this time. Then this writer will be
> > forced to wait and block all subsequent readers.
> > For example:
> > - be scheduled when the read lock of shrinker_rwsem is
> > held in do_shrink_slab()
> > - some shrinker are blocked for too long. Like the case
> > mentioned in the patchset[1].
> >
> > Therefore, many times in history ([2],[3],[4],[5]), some
> > people wanted to replace shrinker_rwsem reader with SRCU,
> > but they all gave up because SRCU was not unconditionally
> > enabled.
> >
> > But now, since commit 1cd0bd06093c ("rcu: Remove CONFIG_SRCU"),
> > the SRCU is unconditionally enabled. So it's time to use
> > SRCU to protect readers who previously held shrinker_rwsem.
> >
> > [1]. https://lore.kernel.org/lkml/20191129214541.3110-1-ptikhomirov@virtuozzo.com/
> > [2]. https://lore.kernel.org/all/1437080113.3596.2.camel@stgolabs.net/
> > [3]. https://lore.kernel.org/lkml/1510609063-3327-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp/
> > [4]. https://lore.kernel.org/lkml/153365347929.19074.12509495712735843805.stgit@localhost.localdomain/
> > [5]. https://lore.kernel.org/lkml/20210927074823.5825-1-sultan@kerneltoast.com/
> >
> > Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
> > ---
> > mm/vmscan.c | 27 +++++++++++----------------
> > 1 file changed, 11 insertions(+), 16 deletions(-)
> >
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index 9f895ca6216c..02987a6f95d1 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -202,6 +202,7 @@ static void set_task_reclaim_state(struct task_struct *task,
> >
> > LIST_HEAD(shrinker_list);
> > DECLARE_RWSEM(shrinker_rwsem);
> > +DEFINE_SRCU(shrinker_srcu);
> >
> > #ifdef CONFIG_MEMCG
> > static int shrinker_nr_max;
> > @@ -706,7 +707,7 @@ void free_prealloced_shrinker(struct shrinker *shrinker)
> > void register_shrinker_prepared(struct shrinker *shrinker)
> > {
> > down_write(&shrinker_rwsem);
>
> I think you could revert the rwsem back to a simple mutex, now.
>
NVM, that's exactly what patch 7 does. :)
next prev parent reply other threads:[~2023-02-23 15:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 13:27 [PATCH v2 0/7] make " Qi Zheng
2023-02-23 13:27 ` [PATCH v2 1/7] mm: vmscan: add a map_nr_max field to shrinker_info Qi Zheng
2023-02-25 8:18 ` Qi Zheng
2023-02-25 15:14 ` Kirill Tkhai
2023-02-25 15:52 ` Qi Zheng
2023-02-26 13:54 ` Qi Zheng
2023-02-23 13:27 ` [PATCH v2 2/7] mm: vmscan: make global slab shrink lockless Qi Zheng
2023-02-23 15:26 ` Rafael Aquini
2023-02-23 15:37 ` Rafael Aquini [this message]
2023-02-24 4:09 ` Qi Zheng
2023-02-23 18:24 ` Sultan Alsawaf
2023-02-23 18:39 ` Paul E. McKenney
2023-02-23 19:18 ` Sultan Alsawaf
2023-02-24 4:00 ` Qi Zheng
2023-02-24 4:16 ` Qi Zheng
2023-02-24 8:20 ` Sultan Alsawaf
2023-02-24 10:12 ` Qi Zheng
2023-02-24 21:02 ` Kirill Tkhai
2023-02-24 21:14 ` Kirill Tkhai
2023-02-25 8:08 ` Qi Zheng
2023-02-25 15:30 ` Kirill Tkhai
2023-02-25 15:57 ` Qi Zheng
2023-02-25 16:17 ` Kirill Tkhai
2023-02-25 16:37 ` Qi Zheng
2023-02-25 21:28 ` Kirill Tkhai
2023-02-26 13:56 ` Qi Zheng
2023-02-23 13:27 ` [PATCH v2 3/7] mm: vmscan: make memcg " Qi Zheng
2023-02-23 13:27 ` [PATCH v2 4/7] mm: shrinkers: make count and scan in shrinker debugfs lockless Qi Zheng
2023-02-23 13:27 ` [PATCH v2 5/7] mm: vmscan: hold write lock to reparent shrinker nr_deferred Qi Zheng
2023-02-23 13:27 ` [PATCH v2 6/7] mm: vmscan: remove shrinker_rwsem from synchronize_shrinkers() Qi Zheng
2023-02-23 13:27 ` [PATCH v2 7/7] mm: shrinkers: convert shrinker_rwsem to mutex Qi Zheng
2023-02-23 18:19 ` [PATCH v2 0/7] make slab shrink lockless Paul E. McKenney
2023-02-24 4:08 ` Qi Zheng
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=Y/eIMXtEJVszprNb@optiplex-fbsd \
--to=aquini@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=paulmck@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=sultan@kerneltoast.com \
--cc=tkhai@ya.ru \
--cc=zhengqi.arch@bytedance.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