From: Miaohe Lin <linmiaohe@huawei.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/mm_init: use helper macro BITS_PER_LONG
Date: Fri, 4 Aug 2023 09:53:17 +0800 [thread overview]
Message-ID: <b1dd7fd9-3454-c6d7-2195-4dfbc295f56d@huawei.com> (raw)
In-Reply-To: <20230803133346.GH2607694@kernel.org>
On 2023/8/3 21:33, Mike Rapoport wrote:
> On Thu, Aug 03, 2023 at 07:40:51PM +0800, Miaohe Lin wrote:
>> It's more readable to use helper macro BITS_PER_LONG. No functional
>> change intended.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.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 66aca3f6accd..2f37dbb5ff9a 100644
>> --- a/mm/mm_init.c
>> +++ b/mm/mm_init.c
>> @@ -79,7 +79,7 @@ void __init mminit_verify_pageflags_layout(void)
>> int shift, width;
>> unsigned long or_mask, add_mask;
>>
>> - shift = 8 * sizeof(unsigned long);
>> + shift = BITS_PER_LONG;
>> width = shift - SECTIONS_WIDTH - NODES_WIDTH - ZONES_WIDTH
>> - LAST_CPUPID_SHIFT - KASAN_TAG_WIDTH - LRU_GEN_WIDTH - LRU_REFS_WIDTH;
>> mminit_dprintk(MMINIT_TRACE, "pageflags_layout_widths",
>> @@ -1431,7 +1431,7 @@ static unsigned long __init usemap_size(unsigned long zone_start_pfn, unsigned l
>> usemapsize = roundup(zonesize, pageblock_nr_pages);
>> usemapsize = usemapsize >> pageblock_order;
>> usemapsize *= NR_PAGEBLOCK_BITS;
>> - usemapsize = roundup(usemapsize, 8 * sizeof(unsigned long));
>> + usemapsize = roundup(usemapsize, BITS_PER_LONG);
>>
>> return usemapsize / 8;
>
> BITS_PER_BYTE instead of 8 here?
Sure, this is even better. Will do.
Thanks.
prev parent reply other threads:[~2023-08-04 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:40 Miaohe Lin
2023-08-03 13:08 ` David Hildenbrand
2023-08-03 13:33 ` Mike Rapoport
2023-08-04 1:53 ` Miaohe Lin [this message]
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=b1dd7fd9-3454-c6d7-2195-4dfbc295f56d@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/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