From: Wei Yang <richard.weiyang@gmail.com>
To: Shivank Garg <shivankg@amd.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
rppt@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/mm_init.c: use round_up() to align movable range
Date: Wed, 12 Feb 2025 00:24:16 +0000 [thread overview]
Message-ID: <20250212002416.rpxemlqtd774qcq6@master> (raw)
In-Reply-To: <c93c4cab-9468-4fce-9b50-8268f50aec42@amd.com>
On Tue, Feb 11, 2025 at 11:43:52PM +0530, Shivank Garg wrote:
>
>
>On 2/7/2025 3:34 PM, Wei Yang wrote:
>> Since MAX_ORDER_NR_PAGES is power of 2, let's use a faster version.
>
>Makes sense to me.
>
>Reviewed-by: Shivank Garg <shivankg@amd.com>
>
Thanks for taking a look.
>
>I noticed two similar instances in the same file
>where round_up() might also be applicable:
>
> mm_init.c (usemap_size):
> usemapsize = roundup(zonesize, pageblock_nr_pages);
> usemapsize = roundup(usemapsize, BITS_PER_LONG);
>
>Since both pageblock_nr_pages (1UL << pageblock_order) and BITS_PER_LONG (32 or 64)
>are powers of 2, these could potentially use round_up() as well. Perhaps
>worth considering in a follow-up patch?
It looks reasonable to me. I would prepare one.
Thanks.
>
>Thanks,
>Shivank
>
>
>
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> ---
>> mm/mm_init.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/mm_init.c b/mm/mm_init.c
>> index dec4084fe15a..99ef70a8b63c 100644
>> --- a/mm/mm_init.c
>> +++ b/mm/mm_init.c
>> @@ -438,7 +438,7 @@ static void __init find_zone_movable_pfns_for_nodes(void)
>> * was requested by the user
>> */
>> required_movablecore =
>> - roundup(required_movablecore, MAX_ORDER_NR_PAGES);
>> + round_up(required_movablecore, MAX_ORDER_NR_PAGES);
>> required_movablecore = min(totalpages, required_movablecore);
>> corepages = totalpages - required_movablecore;
>>
>> @@ -549,7 +549,7 @@ static void __init find_zone_movable_pfns_for_nodes(void)
>> unsigned long start_pfn, end_pfn;
>>
>> zone_movable_pfn[nid] =
>> - roundup(zone_movable_pfn[nid], MAX_ORDER_NR_PAGES);
>> + round_up(zone_movable_pfn[nid], MAX_ORDER_NR_PAGES);
>>
>> get_pfn_range_for_nid(nid, &start_pfn, &end_pfn);
>> if (zone_movable_pfn[nid] >= end_pfn)
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-02-12 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 10:04 Wei Yang
2025-02-11 18:13 ` Shivank Garg
2025-02-12 0:24 ` Wei Yang [this message]
2025-02-13 6:29 ` Mike Rapoport
2025-02-13 6:37 ` Anshuman Khandual
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=20250212002416.rpxemlqtd774qcq6@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=shivankg@amd.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