From: Chengming Zhou <zhouchengming@bytedance.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: nphamcs@gmail.com, yosryahmed@google.com,
Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
hannes@cmpxchg.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mm/zsmalloc: remove migrate_write_lock_nested()
Date: Tue, 20 Feb 2024 12:51:46 +0800 [thread overview]
Message-ID: <4f3c6c96-3bea-4369-a2de-e3c559505bba@bytedance.com> (raw)
In-Reply-To: <20240220044825.GD11472@google.com>
On 2024/2/20 12:48, Sergey Senozhatsky wrote:
> On (24/02/19 13:33), Chengming Zhou wrote:
>> static void migrate_write_unlock(struct zspage *zspage)
>> {
>> write_unlock(&zspage->lock);
>> @@ -2003,19 +1997,17 @@ static unsigned long __zs_compact(struct zs_pool *pool,
>> dst_zspage = isolate_dst_zspage(class);
>> if (!dst_zspage)
>> break;
>> - migrate_write_lock(dst_zspage);
>> }
>>
>> src_zspage = isolate_src_zspage(class);
>> if (!src_zspage)
>> break;
>>
>> - migrate_write_lock_nested(src_zspage);
>> -
>> + migrate_write_lock(src_zspage);
>> migrate_zspage(pool, src_zspage, dst_zspage);
>> - fg = putback_zspage(class, src_zspage);
>> migrate_write_unlock(src_zspage);
>>
>> + fg = putback_zspage(class, src_zspage);
>
> Hmm. Lockless putback doesn't look right to me. We modify critical
> zspage fileds in putback_zspage().
Which I think is protected by pool->lock, right? We already held it.
>
>> if (fg == ZS_INUSE_RATIO_0) {
>> free_zspage(pool, class, src_zspage);
>> pages_freed += class->pages_per_zspage;
>> @@ -2025,7 +2017,6 @@ static unsigned long __zs_compact(struct zs_pool *pool,
>> if (get_fullness_group(class, dst_zspage) == ZS_INUSE_RATIO_100
>> || spin_is_contended(&pool->lock)) {
>> putback_zspage(class, dst_zspage);
>> - migrate_write_unlock(dst_zspage);
>> dst_zspage = NULL;
>>
>> spin_unlock(&pool->lock);
>> @@ -2034,15 +2025,12 @@ static unsigned long __zs_compact(struct zs_pool *pool,
>> }
>> }
>>
>> - if (src_zspage) {
>> + if (src_zspage)
>> putback_zspage(class, src_zspage);
>> - migrate_write_unlock(src_zspage);
>> - }
>>
>> - if (dst_zspage) {
>> + if (dst_zspage)
>> putback_zspage(class, dst_zspage);
>> - migrate_write_unlock(dst_zspage);
>> - }
next prev parent reply other threads:[~2024-02-20 4:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 13:33 [PATCH 0/3] mm/zsmalloc: fix and optimize objects/page migration Chengming Zhou
2024-02-19 13:33 ` [PATCH 1/3] mm/zsmalloc: fix migrate_write_lock() when !CONFIG_COMPACTION Chengming Zhou
2024-02-19 13:33 ` [PATCH 2/3] mm/zsmalloc: remove migrate_write_lock_nested() Chengming Zhou
2024-02-20 4:48 ` Sergey Senozhatsky
2024-02-20 4:51 ` Chengming Zhou [this message]
2024-02-20 4:53 ` Sergey Senozhatsky
2024-02-20 4:59 ` Chengming Zhou
2024-02-20 5:02 ` Sergey Senozhatsky
2024-02-19 13:33 ` [PATCH 3/3] mm/zsmalloc: remove unused zspage->isolated Chengming Zhou
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=4f3c6c96-3bea-4369-a2de-e3c559505bba@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=yosryahmed@google.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
all inboxes | Powered by JetHome®