From: Donet Tom <donettom@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
Oscar Salvador <osalvador@suse.de>, Zi Yan <ziy@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ritesh Harjani <ritesh.list@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alison Schofield <alison.schofield@intel.com>,
Yury Norov <yury.norov@gmail.com>,
Dave Jiang <dave.jiang@intel.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Nilay Shroff <nilay@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v7 1/5] drivers/base/node: Optimize memory block registration to reduce boot time
Date: Wed, 4 Jun 2025 18:47:01 +0530 [thread overview]
Message-ID: <9f7ae0e6-4640-418d-a4db-dba594377ac2@linux.ibm.com> (raw)
In-Reply-To: <b355e72d-0284-4a31-84e3-ae4a79ad922f@redhat.com>
On 6/4/25 3:15 PM, David Hildenbrand wrote:
> On 04.06.25 05:07, Andrew Morton wrote:
>> On Wed, 28 May 2025 12:18:00 -0500 Donet Tom <donettom@linux.ibm.com>
>> wrote:
>>
>>> During node device initialization, `memory blocks` are registered under
>>> each NUMA node. The `memory blocks` to be registered are identified
>>> using
>>> the node’s start and end PFNs, which are obtained from the node's
>>> pg_data
>>
>> It's quite unconventional to omit the [0/N] changelog. This omission
>> somewhat messed up my processes so I added a one-liner to this.
>>
>
> Yeah, I was assuming that I simply did not get cc'ed on the cover
> letter, but there is actually none.
>
> Donet please add that in the future. git can do this using
> --cover-letter.
Sure,
I will add cover letter in next revision.
>
>>>
>>> ...
>>>
>>> Test Results on My system with 32TB RAM
>>> =======================================
>>> 1. Boot time with CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled.
>>>
>>> Without this patch
>>> ------------------
>>> Startup finished in 1min 16.528s (kernel)
>>>
>>> With this patch
>>> ---------------
>>> Startup finished in 17.236s (kernel) - 78% Improvement
>>
>> Well someone is in for a nice surprise.
>>
>>> 2. Boot time with CONFIG_DEFERRED_STRUCT_PAGE_INIT disabled.
>>>
>>> Without this patch
>>> ------------------
>>> Startup finished in 28.320s (kernel)
>>
>> what. CONFIG_DEFERRED_STRUCT_PAGE_INIT is supposed to make bootup
>> faster.
>
> Right, that's weird. Especially that it is still slower after these
> changes.
>
> CONFIG_DEFERRED_STRUCT_PAGE_INIT should be initializing in parallel
> which ... should be faster.
>
> @Donet, how many CPUs and nodes does your system have? Can you
> identify what is taking longer than without
> CONFIG_DEFERRED_STRUCT_PAGE_INIT?
My system has,
CPU - 1528
Node - 16
Memory - 31TB
I ran the same test with and without CONFIG_DEFERRED_STRUCT_PAGE_INIT,
and the boot time was consistently higher with
CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled.
I'm still investigating this. I'll check further and get back to you.
CONFIG_DEFERRED_STRUCT_PAGE_INIT enabled
----------------------------------------------------------------------
1. Startup finished in 12.959s (kernel)
2. Startup finished in 13.036s (kernel)
3. Startup finished in 12.944s (kernel)
CONFIG_DEFERRED_STRUCT_PAGE_INIT disabled
-----------------------------------------------------------------------
1. Startup finished in 12.234s (kernel)
2. Startup finished in 12.287s (kernel)
3. Startup finished in 12.230s (kernel)
Thanks
Donet
next prev parent reply other threads:[~2025-06-04 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:18 [PATCH v7 1/5] drivers/base/node: Optimize memory block registration to reduce boot time Donet Tom
2025-05-28 17:18 ` [PATCH v7 2/5] drivers/base/node: remove register_mem_block_under_node_early() Donet Tom
2025-05-28 17:18 ` [PATCH v7 3/5] drivers/base/node: Remove register_memory_blocks_under_node() function call from register_one_node Donet Tom
2025-05-28 17:18 ` [PATCH v7 4/5] drivers/base/node: Rename register_memory_blocks_under_node() and remove context argument Donet Tom
2025-05-28 17:18 ` [PATCH v7 5/5] drivers/base/node: Rename __register_one_node() to register_one_node() Donet Tom
2025-06-04 3:07 ` [PATCH v7 1/5] drivers/base/node: Optimize memory block registration to reduce boot time Andrew Morton
2025-06-04 9:45 ` David Hildenbrand
2025-06-04 13:17 ` Donet Tom [this message]
2025-06-04 13:30 ` David Hildenbrand
2025-06-04 15:57 ` Donet Tom
2025-06-04 13:25 ` Donet Tom
2025-06-04 9:38 ` David Hildenbrand
2025-06-04 13:27 ` Donet Tom
2025-06-04 13:30 ` David Hildenbrand
2025-06-09 14:03 ` [Fixup PATCH] drivers/base/node: Restored the removed extra line Donet Tom
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=9f7ae0e6-4640-418d-a4db-dba594377ac2@linux.ibm.com \
--to=donettom@linux.ibm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=dakr@kernel.org \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=nilay@linux.ibm.com \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).