From: ranxiaokai627@163.com
To: baolin.wang@linux.alibaba.com
Cc: akpm@linux-foundation.org, hughd@google.com, leitao@debian.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
ran.xiaokai@zte.com.cn, ranxiaokai627@163.com
Subject: Re: [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string()
Date: Wed, 13 May 2026 08:25:58 +0000 [thread overview]
Message-ID: <20260513082558.50743-1-ranxiaokai627@163.com> (raw)
In-Reply-To: <7b8cb44c-a098-4430-a8ef-142fa7a19087@linux.alibaba.com>
>CC Breno and Lorenzo
>
>On 5/12/26 8:05 PM, ranxiaokai627@163.com wrote:
>> From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
>>
>> Inspired by commit 82d9ff648c6c ("mm: huge_memory: refactor
>> anon_enabled_store() with set_anon_enabled_mode()"), refactor
>> thpsize_shmem_enabled_store() using sysfs_match_string().
>> This eliminates the duplicated spin_lock/unlock(), set/clear_bit(),
>> calls across all branches, reducing code duplication.
>>
>> Tested with selftests ./run_kselftest.sh -t mm:ksft_thp.sh,
>> all test cases passed.
>>
>> Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
>> ---
>
>Thanks for doing this.
>
>> mm/shmem.c | 88 ++++++++++++++++++++++++++----------------------------
>> 1 file changed, 43 insertions(+), 45 deletions(-)
>>
>> diff --git a/mm/shmem.c b/mm/shmem.c
>> index 3b5dc21b323c..0cc7872cc576 100644
>> --- a/mm/shmem.c
>> +++ b/mm/shmem.c
>> @@ -5526,6 +5526,29 @@ static ssize_t shmem_enabled_store(struct kobject *kobj,
>> struct kobj_attribute shmem_enabled_attr = __ATTR_RW(shmem_enabled);
>> static DEFINE_SPINLOCK(huge_shmem_orders_lock);
>>
>
>We are already under the lock, so you can use non-atomic functions like
>commit 82d9ff648c6c does: __test_and_set_bit/__test_and_clear_bit.
>
>> + spin_unlock(&huge_shmem_orders_lock);
>>
>> - if (ret > 0) {
>> - int err = start_stop_khugepaged();
>> + err = start_stop_khugepaged();
>> + if (err)
>
>Moreover, I think we can follow commit 82d9ff648c6c's approach: if
>nothing changed, we don't need to call start_stop_khugepaged().
Thanks for the review.
Yes, indeed, We can further optimize this by following the approach
in commit 82d9ff648c6c.
It seems odd to still call set_recommended_min_free_kbytes() when the
mode hasn't changed. Maybe this is to handle the case where the user
modified /proc/sys/vm/min_free_kbytes in this timewindow?
I'll follow the existing logic and send a v2.
next prev parent reply other threads:[~2026-05-13 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:05 [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string() ranxiaokai627
2026-05-12 12:05 ` [PATCH 2/2] mm: huge_memory: refactor thpsize_shmem_enabled_show() with helper arrays ranxiaokai627
2026-05-13 3:04 ` [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string() Baolin Wang
2026-05-13 8:25 ` ranxiaokai627 [this message]
2026-05-13 8:56 ` Breno Leitao
2026-05-13 9:03 ` Lorenzo Stoakes
2026-05-13 9:38 ` David Hildenbrand (Arm)
2026-05-13 9:40 ` Lorenzo Stoakes
2026-05-13 10:09 ` ranxiaokai627
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=20260513082558.50743-1-ranxiaokai627@163.com \
--to=ranxiaokai627@163.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=hughd@google.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=ran.xiaokai@zte.com.cn \
/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