From: Leon Hwang <leon.hwang@linux.dev>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: akpm@linux-foundation.org, david@redhat.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-new 1/1] mm/khugepaged: Factor out common logic in [scan,alloc]_sleep_millisecs_store()
Date: Mon, 20 Oct 2025 23:32:17 +0800 [thread overview]
Message-ID: <1a207072-8623-40ef-bf3c-0edc1c6304ea@linux.dev> (raw)
In-Reply-To: <7d9b4ac6-b0c2-4a0e-bee1-23f7a82eea72@lucifer.local>
On 2025/10/20 21:53, Lorenzo Stoakes wrote:
> On Mon, Oct 20, 2025 at 07:53:50PM +0800, Leon Hwang wrote:
>> Both scan_sleep_millisecs_store() and alloc_sleep_millisecs_store()
>> perform the same operations: parse the input value, update their
>> respective sleep interval, reset khugepaged_sleep_expire, and wake up
>> the khugepaged thread.
>>
>> Factor out this duplicated logic into a helper function
>> __sleep_millisecs_store(), and simplify both store functions.
>>
>> No functional change intended.
>>
>> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
>
> Thanks this is a decent cleanup, with the nit(s0 below addressed LGTM, so:
>
> Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
Thanks for the review, Lorenzo.
>> ---
>> mm/khugepaged.c | 29 ++++++++++++++---------------
>> 1 file changed, 14 insertions(+), 15 deletions(-)
>>
>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>> index 0341c3d13e9e..0b7915015e9e 100644
>> --- a/mm/khugepaged.c
>> +++ b/mm/khugepaged.c
>> @@ -129,9 +129,8 @@ static ssize_t scan_sleep_millisecs_show(struct kobject *kobj,
>> return sysfs_emit(buf, "%u\n", khugepaged_scan_sleep_millisecs);
>> }
>>
>> -static ssize_t scan_sleep_millisecs_store(struct kobject *kobj,
>> - struct kobj_attribute *attr,
>> - const char *buf, size_t count)
>> +static ssize_t __sleep_millisecs_store(const char *buf, size_t count,
>> + unsigned int *millisecs)
>> {
>> unsigned int msecs;
>> int err;
>> @@ -140,12 +139,21 @@ static ssize_t scan_sleep_millisecs_store(struct kobject *kobj,
>> if (err)
>> return -EINVAL;
>>
>> - khugepaged_scan_sleep_millisecs = msecs;
>> + *millisecs = msecs;
>> khugepaged_sleep_expire = 0;
>> wake_up_interruptible(&khugepaged_wait);
>>
>> return count;
>> }
>> +
>> +static ssize_t scan_sleep_millisecs_store(struct kobject *kobj,
>> + struct kobj_attribute *attr,
>> + const char *buf, size_t count)
>> +{
>> + unsigned int *millisecs = &khugepaged_scan_sleep_millisecs;
>> +
>> + return __sleep_millisecs_store(buf, count, millisecs);
>
> I think this'd be much clearer as:
> > return __sleep_millisecs_store(buf, count,
&khugepaged_alloc_scan_millisecs);
>
>> +}
>> static struct kobj_attribute scan_sleep_millisecs_attr =
>> __ATTR_RW(scan_sleep_millisecs);
>>
>> @@ -160,18 +168,9 @@ static ssize_t alloc_sleep_millisecs_store(struct kobject *kobj,
>> struct kobj_attribute *attr,
>> const char *buf, size_t count)
>> {
>> - unsigned int msecs;
>> - int err;
>> -
>> - err = kstrtouint(buf, 10, &msecs);
>> - if (err)
>> - return -EINVAL;
>> + unsigned int *millisecs = &khugepaged_alloc_sleep_millisecs;
>>
>> - khugepaged_alloc_sleep_millisecs = msecs;
>> - khugepaged_sleep_expire = 0;
>> - wake_up_interruptible(&khugepaged_wait);
>> -
>> - return count;
>> + return __sleep_millisecs_store(buf, count, millisecs);
>> }
>
> I think this'd be much clearer as:
>
> return __sleep_millisecs_store(buf, count, &khugepaged_alloc_sleep_millisecs);
>
Indeed, your suggestion makes the code clearer.
I'll update both occurrences in the next revision.
Thanks,
Leon
>> static struct kobj_attribute alloc_sleep_millisecs_attr =
>> __ATTR_RW(alloc_sleep_millisecs);
>> --
>> 2.51.0
>>
next prev parent reply other threads:[~2025-10-20 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 11:53 [PATCH mm-new 1/1] mm/khugepaged: Factor out common logic in [scan,alloc]_sleep_millisecs_store() Leon Hwang
2025-10-20 13:53 ` Lorenzo Stoakes
2025-10-20 15:32 ` Leon Hwang [this message]
2025-10-20 20:01 ` Zi Yan
2025-10-21 2:14 ` Lance Yang
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=1a207072-8623-40ef-bf3c-0edc1c6304ea@linux.dev \
--to=leon.hwang@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.