From: David Hildenbrand <david@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Oscar Salvador <osalvador@suse.de>,
Gregory Price <gourry@gourry.net>,
linux-mm@kvack.org, linux-acpi@vger.kernel.org,
kernel-team@meta.com, x86@kernel.org,
linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
luto@kernel.org, peterz@infradead.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com, rafael@kernel.org,
lenb@kernel.org, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, dan.j.williams@intel.com,
Jonathan.Cameron@huawei.com, alison.schofield@intel.com,
rrichter@amd.com, bfaccini@nvidia.com, haibo1.xu@intel.com,
dave.jiang@intel.com, Ira Weiny <ira.weiny@intel.com>,
Fan Ni <fan.ni@samsung.com>
Subject: Re: [PATCH v8 0/3] memory,x86,acpi: hotplug memory alignment advisement
Date: Wed, 2 Apr 2025 12:07:29 +0200 [thread overview]
Message-ID: <8317bce8-1a50-4870-b29a-f8a6b9bb66c6@redhat.com> (raw)
In-Reply-To: <Z-0F4Fm0byd0Co3v@kernel.org>
On 02.04.25 11:39, Mike Rapoport wrote:
> On Tue, Apr 01, 2025 at 09:08:31PM +0200, David Hildenbrand wrote:
>> On 01.04.25 20:53, Oscar Salvador wrote:
>>> On Mon, Jan 27, 2025 at 10:34:02AM -0500, Gregory Price wrote:
>>>> v8: nits and tag pickups
>>>>
>>>> When physical address regions are not aligned to memory block size,
>>>> the misaligned portion is lost (stranded capacity).
>>>>
>>>> Block size (min/max/selected) is architecture defined. Most architectures
>>>> tend to use the minimum block size or some simplistic heurist. On x86,
>>>> memory block size increases up to 2GB, and is otherwise fitted to the
>>>> alignment of non-hotplug (i.e. not special purpose memory).
>>>
>>> I wonder if something like this could help us in improving the
>>> ridiculous situation of having 16MB memory-block size on powerpc.
>>
>> They have this granularity because ... they want to add/remove memory in
>> 16MiB on some powerpc dlpar machines :(
>
> I'm not sure they do it today, there's a comment in near define of that 16M
> in arch/powerpc/mm/init_64.c:
>
> /*
> * Outside hotplug the kernel uses this value to map the kernel direct map
> * with radix. To be compatible with older kernels, let's keep this value
> * as 16M which is also SECTION_SIZE with SPARSEMEM. We can ideally map
> * things with 1GB size in the case where we don't support hotplug.
> */
> > and their SECTION_SIZE didn't change since 2005.
> Quite possible that they'll be fine with increasing their
> DEFAULT_MEMORY_BLOCK_SIZE.
At least modern PowerVM on Power10 seems to support LMBs of 128 MiB.
"Based on this data, Power10 initially only supported LMB sizes of 128MB
and 256MB." The default usually seems to be 256 MiB.
In reality, the expectation is that the hypervisor will always
communicate the LMB such that the memory block size will be set to that.
Assuming we'd increase DEFAULT_MEMORY_BLOCK_SIZE to 128MiB, we might
also be able to increase SECTION_SIZE to 128 MiB I assume.
Not sure about older PowerVM / systems.
[1]
https://community.ibm.com/community/user/power/blogs/pete-heyrman1/2024/03/06/power10-lmb-sizes
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-02 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 15:34 [PATCH v8 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2025-01-27 15:34 ` [PATCH v8 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2025-04-01 18:50 ` Oscar Salvador
2025-01-27 15:34 ` [PATCH v8 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2025-04-01 18:51 ` Oscar Salvador
2025-01-27 15:34 ` [PATCH v8 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2025-04-01 18:52 ` Oscar Salvador
2025-04-01 18:33 ` [PATCH v8 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2025-04-01 18:53 ` Oscar Salvador
2025-04-01 19:08 ` David Hildenbrand
2025-04-02 9:39 ` Mike Rapoport
2025-04-02 10:07 ` David Hildenbrand [this message]
2025-04-01 19:44 ` Dan Williams
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=8317bce8-1a50-4870-b29a-f8a6b9bb66c6@redhat.com \
--to=david@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bfaccini@nvidia.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=haibo1.xu@intel.com \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=kernel-team@meta.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=rrichter@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).