From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Kirill Tkhai <tkhai@ya.ru>,
akpm@linux-foundation.org, hannes@cmpxchg.org,
shakeelb@google.com, mhocko@kernel.org, roman.gushchin@linux.dev,
muchun.song@linux.dev, david@redhat.com, shy828301@gmail.com,
rppt@kernel.org
Cc: 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,
christian.koenig@amd.com
Subject: Re: [PATCH v4 7/8] mm: vmscan: remove shrinker_rwsem from synchronize_shrinkers()
Date: Thu, 9 Mar 2023 15:06:25 +0800 [thread overview]
Message-ID: <07078623-b7ef-ceb4-eccc-8872a4067273@bytedance.com> (raw)
In-Reply-To: <bc829246-4606-cc8d-4a4f-da285255f5a3@ya.ru>
Hi Kirill,
On 2023/3/9 06:39, Kirill Tkhai wrote:
> On 07.03.2023 09:56, Qi Zheng wrote:
>> Now there are no readers of shrinker_rwsem, so
>> synchronize_shrinkers() does not need to hold the
>> writer of shrinker_rwsem to wait for all running
>> shinkers to complete, synchronize_srcu() is enough.
>>
>> Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
>> ---
>> mm/vmscan.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 7aaf6f94ac1b..ac7ab4aa344f 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -796,15 +796,11 @@ EXPORT_SYMBOL(unregister_shrinker);
>> /**
>> * synchronize_shrinkers - Wait for all running shrinkers to complete.
>> *
>> - * This is equivalent to calling unregister_shrink() and register_shrinker(),
>> - * but atomically and with less overhead. This is useful to guarantee that all
>> - * shrinker invocations have seen an update, before freeing memory, similar to
>> - * rcu.
>> + * This is useful to guarantee that all shrinker invocations have seen an
>> + * update, before freeing memory.
>> */
>> void synchronize_shrinkers(void)
>> {
>> - down_write(&shrinker_rwsem);
>> - up_write(&shrinker_rwsem);
>> atomic_inc(&shrinker_srcu_generation);
>> synchronize_srcu(&shrinker_srcu);
>> }
>
> Just curious, callers of synchronize_shrinkers() don't want to have parallel register_shrinker() and unregister_shrink() are completed?
> Here we only should wait for parallel shrink_slab(), correct?
I think yes.
The synchronize_shrinkers() is currently only used by TTM pool.
In TTM pool, a shrinker named "drm-ttm_pool" is registered, and
the scan_objects callback will pick an entry from its own shrinker_list:
ttm_pool_shrink
--> spin_lock(&shrinker_lock);
pt = list_first_entry(&shrinker_list, typeof(*pt), shrinker_list);
list_move_tail(&pt->shrinker_list, &shrinker_list);
spin_unlock(&shrinker_lock);
These entries have been removed from shrinker_list before calling
synchronize_shrinkers():
ttm_pool_fini
--> ttm_pool_type_fini
--> spin_lock(&shrinker_lock);
list_del(&pt->shrinker_list);
spin_unlock(&shrinker_lock);
synchronize_shrinkers
So IIUC, we only need to wait for the parallel shrink_slab() here. Like
its comment says:
/* We removed the pool types from the LRU, but we need to also make sure
* that no shrinker is concurrently freeing pages from the pool.
*/
+ CC: Christian König :)
Thanks,
Qi
next prev parent reply other threads:[~2023-03-09 7:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 6:55 [PATCH v4 0/8] make slab shrink lockless Qi Zheng
2023-03-07 6:55 ` [PATCH v4 1/8] mm: vmscan: add a map_nr_max field to shrinker_info Qi Zheng
2023-03-08 14:40 ` Vlastimil Babka
2023-03-08 22:13 ` Kirill Tkhai
2023-03-09 6:33 ` Qi Zheng
2023-03-07 6:55 ` [PATCH v4 2/8] mm: vmscan: make global slab shrink lockless Qi Zheng
2023-03-08 15:02 ` Vlastimil Babka
2023-03-08 22:18 ` Kirill Tkhai
2023-03-07 6:56 ` [PATCH v4 3/8] mm: vmscan: make memcg " Qi Zheng
2023-03-08 22:23 ` Kirill Tkhai
2023-03-08 22:46 ` Vlastimil Babka
2023-03-09 6:47 ` Qi Zheng
2023-03-07 6:56 ` [PATCH v4 4/8] mm: vmscan: add shrinker_srcu_generation Qi Zheng
2023-03-09 9:23 ` Vlastimil Babka
2023-03-09 10:12 ` Qi Zheng
2023-03-07 6:56 ` [PATCH v4 5/8] mm: shrinkers: make count and scan in shrinker debugfs lockless Qi Zheng
2023-03-09 9:36 ` Vlastimil Babka
2023-03-09 9:39 ` Vlastimil Babka
2023-03-09 10:14 ` Qi Zheng
2023-03-09 19:30 ` Kirill Tkhai
2023-03-07 6:56 ` [PATCH v4 6/8] mm: vmscan: hold write lock to reparent shrinker nr_deferred Qi Zheng
2023-03-09 9:36 ` Vlastimil Babka
2023-03-07 6:56 ` [PATCH v4 7/8] mm: vmscan: remove shrinker_rwsem from synchronize_shrinkers() Qi Zheng
2023-03-08 22:39 ` Kirill Tkhai
2023-03-09 7:06 ` Qi Zheng [this message]
2023-03-09 8:11 ` Christian König
2023-03-09 8:32 ` Qi Zheng
2023-03-09 19:34 ` Kirill Tkhai
2023-03-09 9:40 ` Vlastimil Babka
2023-03-09 19:34 ` Kirill Tkhai
2023-03-07 6:56 ` [PATCH v4 8/8] mm: shrinkers: convert shrinker_rwsem to mutex Qi Zheng
2023-03-09 9:42 ` Vlastimil Babka
2023-03-09 19:49 ` Kirill Tkhai
2023-03-07 22:20 ` [PATCH v4 0/8] make slab shrink lockless Andrew Morton
2023-03-08 11:59 ` 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=07078623-b7ef-ceb4-eccc-8872a4067273@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--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=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=sultan@kerneltoast.com \
--cc=tkhai@ya.ru \
/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