linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/numa_memblks: Use SZ_1M macro to denote bytes to MB conversion
Date: Wed, 20 Aug 2025 06:09:14 +0530	[thread overview]
Message-ID: <CALzOmR2zOpiN_u1GfudY8QKWOf=w3ytOPuK-dznY7bqKJgJGnA@mail.gmail.com> (raw)
In-Reply-To: <aKSNED01R-AaclOT@kernel.org>

On Tue, Aug 19, 2025 at 8:11 PM Mike Rapoport <rppt@kernel.org> wrote:
>
> On Tue, Aug 19, 2025 at 02:21:44PM +0530, pratyush.brahma@oss.qualcomm.com wrote:
> > From: Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
> >
> > Replace the manual bitwise conversion of bytes to MB with
> > SZ_1M macro, a standard macro used within the mm subsystem,
> > to improve readability.
>
> There are few others:
>
> $ git grep '>> 20' mm/
> mm/memblock.c:          mem_size_mb = memblock_phys_mem_size() >> 20;
> mm/memblock.c:                 (nr_pages << PAGE_SHIFT) >> 20, mem_size_mb);
> mm/numa_emulation.c:           nid, eb->start, eb->end - 1, (eb->end - eb->start) >> 20);
> mm/numa_emulation.c:                    size >> 20, min_size >> 20);
>
> It makes sense to replace all of them in one patch.
Thanks for checking. Will send an updated patch in the next iteration.
>
> > Signed-off-by: Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
> > ---
> >  mm/numa_memblks.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/numa_memblks.c b/mm/numa_memblks.c
> > index 541a99c4071a67e5b0ef66f4136dee268a880003..a47aa262a33366337c38ccc7c7064da818523dd2 100644
> > --- a/mm/numa_memblks.c
> > +++ b/mm/numa_memblks.c
> > @@ -427,9 +427,9 @@ static int __init numa_register_meminfo(struct numa_meminfo *mi)
> >               unsigned long pfn_align = node_map_pfn_alignment();
> >
> >               if (pfn_align && pfn_align < PAGES_PER_SECTION) {
> > -                     unsigned long node_align_mb = PFN_PHYS(pfn_align) >> 20;
> > +                     unsigned long node_align_mb = PFN_PHYS(pfn_align) / SZ_1M;
> >
> > -                     unsigned long sect_align_mb = PFN_PHYS(PAGES_PER_SECTION) >> 20;
> > +                     unsigned long sect_align_mb = PFN_PHYS(PAGES_PER_SECTION) / SZ_1M;
> >
> >                       pr_warn("Node alignment %luMB < min %luMB, rejecting NUMA config\n",
> >                               node_align_mb, sect_align_mb);
> >
> > ---
> > base-commit: c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9
> > change-id: 20250819-numa-memblks-refac-7b4b5017b598
> >
> > Best regards,
> > --
> > Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
> >
>
> --
> Sincerely yours,
> Mike.
Thanks & Regards
Pratyush


      reply	other threads:[~2025-08-20  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  8:51 pratyush.brahma
2025-08-19 14:41 ` Mike Rapoport
2025-08-20  0:39   ` Pratyush Brahma [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='CALzOmR2zOpiN_u1GfudY8QKWOf=w3ytOPuK-dznY7bqKJgJGnA@mail.gmail.com' \
    --to=pratyush.brahma@oss.qualcomm.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