From: pratyush.brahma@oss.qualcomm.com
To: Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
Subject: [PATCH 0/2] (no cover subject)
Date: Fri, 26 Sep 2025 16:04:48 +0530 [thread overview]
Message-ID: <20250926-numa-emu-v1-0-714f2691bf8b@oss.qualcomm.com> (raw)
mm/numa_emulation: Code refactoring to improve modularity and
readability
This series intends to improve the code readability by using
existing macros instead of hardcoded values for size and improves
the modularity by moving the size calculation for emulated blocks
to a separate function.
Signed-off-by: Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
---
Pratyush Brahma (2):
mm/numa_emulation: Refactor NUMA emulation size handling to use kernel macros
mm/numa_emulation: Move the size calculation in split_nodes_interleave() to a separate function
mm/numa_emulation.c | 47 ++++++++++++++++++++++++++++++-----------------
1 file changed, 30 insertions(+), 17 deletions(-)
---
base-commit: 4ff71af020ae59ae2d83b174646fc2ad9fcd4dc4
change-id: 20250926-numa-emu-6e6c27bd8f6f
Best regards,
--
Pratyush Brahma <pratyush.brahma@oss.qualcomm.com>
next reply other threads:[~2025-09-26 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 10:34 pratyush.brahma [this message]
2025-09-26 10:34 ` [PATCH 1/2] mm/numa_emulation: Refactor NUMA emulation size handling to use kernel macros pratyush.brahma
2025-09-26 10:34 ` [PATCH 2/2] mm/numa_emulation: Move the size calculation in split_nodes_interleave() to a separate function pratyush.brahma
2025-09-26 13:48 ` Christophe Leroy
2025-09-29 7:16 ` Pratyush Brahma
2025-10-07 2:48 ` Pratyush Brahma
2025-10-07 4:23 ` [PATCH 0/2] (no cover subject) 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=20250926-numa-emu-v1-0-714f2691bf8b@oss.qualcomm.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