From: David Hildenbrand <david@redhat.com>
To: Gregory Price <gourry@gourry.net>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-mm@kvack.org,
linux-cxl@kvack.org, Jonathan.Cameron@huawei.com,
dan.j.williams@intel.com, rrichter@amd.com, Terry.Bowman@amd.com,
dave.jiang@intel.com, ira.weiny@intel.com,
alison.schofield@intel.com, 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, osalvador@suse.de, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, rppt@kernel.org
Subject: Re: [PATCH v3 2/3] x86: probe memory block size advisement value during mm init
Date: Tue, 29 Oct 2024 14:52:17 +0100 [thread overview]
Message-ID: <c0decc3e-8b3a-40e1-a997-f4b6f500f546@redhat.com> (raw)
In-Reply-To: <ZyDnmUlXym7gDkCh@PC2K9PVX.TheFacebook.com>
On 29.10.24 14:48, Gregory Price wrote:
> On Tue, Oct 29, 2024 at 01:40:38PM +0100, David Hildenbrand wrote:
>> On 22.10.24 23:34, Gregory Price wrote:
>>> Systems with hotplug may provide an advisement value on what the
>>> memblock size should be. Probe this value when the rest of the
>>> configuration values are considered.
>>>
>>> The new heuristic is as follows
>>>
>>> 1) set_memory_block_size_order value if already set (cmdline param)
>>> 2) minimum block size if memory is less than large block limit
>>> 3) if no hotplug advice: Max block size if system is bare-metal,
>>> otherwise use end of memory alignment.
>>> 4) if hotplug advice: lesser of advice and end of memory alignment.
>>>
>>> Suggested-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Gregory Price <gourry@gourry.net>
>>> ---
>>> arch/x86/mm/init_64.c | 14 +++++++++-----
>>> 1 file changed, 9 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
>>> index ff253648706f..93d669f467f7 100644
>>> --- a/arch/x86/mm/init_64.c
>>> +++ b/arch/x86/mm/init_64.c
>>> @@ -1452,13 +1452,17 @@ static unsigned long probe_memory_block_size(void)
>>> }
>>> /*
>>> - * Use max block size to minimize overhead on bare metal, where
>>> - * alignment for memory hotplug isn't a concern.
>>> + * When hotplug alignment is not a concern, maximize blocksize
>>> + * to minimize overhead. Otherwise, align to the lesser of advice
>>> + * alignment and end of memory alignment.
>>> */
>>> - if (!boot_cpu_has(X86_FEATURE_HYPERVISOR)) {
>>> + bz = memory_block_probe_max_size();
>>> + if (!bz) {
>>> bz = MAX_BLOCK_SIZE;
>>> - goto done;
>>> - }
>>> + if (!boot_cpu_has(X86_FEATURE_HYPERVISOR))
>>> + goto done;
>>> + } else
>>> + bz = max(min(bz, MAX_BLOCK_SIZE), MIN_MEMORY_BLOCK_SIZE);
>>> /* Find the largest allowed block size that aligns to memory end */
>>> for (bz = MAX_BLOCK_SIZE; bz > MIN_MEMORY_BLOCK_SIZE; bz >>= 1) {
> ^^^^^^^^^^^^^^^^^^^^^^^^
>>
>>
>> Acked-by: David Hildenbrand <david@redhat.com>
>
> Will pick this up but wanted to point out the silly bug above.
> This version completely ignores the advise lol.
>
> Changing to below
>
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index 93d669f467f7..01876629f21f 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -1465,7 +1465,7 @@ static unsigned long probe_memory_block_size(void)
> bz = max(min(bz, MAX_BLOCK_SIZE), MIN_MEMORY_BLOCK_SIZE);
>
> /* Find the largest allowed block size that aligns to memory end */
> - for (bz = MAX_BLOCK_SIZE; bz > MIN_MEMORY_BLOCK_SIZE; bz >>= 1) {
> + for (; bz > MIN_MEMORY_BLOCK_SIZE; bz >>= 1) {
> if (IS_ALIGNED(boot_mem_end, bz))
> break;
Heh, yes, I think I suggested that in my quick draft.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-10-29 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 21:34 [PATCH v3 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2024-10-22 21:34 ` [PATCH v3 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2024-10-28 17:27 ` Mike Rapoport
2024-10-29 12:39 ` David Hildenbrand
2024-10-22 21:34 ` [PATCH v3 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2024-10-29 12:40 ` David Hildenbrand
2024-10-29 13:48 ` Gregory Price
2024-10-29 13:52 ` David Hildenbrand [this message]
2024-10-22 21:34 ` [PATCH v3 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2024-10-28 17:24 ` Mike Rapoport
2024-10-28 20:55 ` Gregory Price
2024-10-29 12:42 ` David Hildenbrand
2024-10-29 13:20 ` Gregory Price
2024-10-29 16:31 ` Mike Rapoport
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=c0decc3e-8b3a-40e1-a997-f4b6f500f546@redhat.com \
--to=david@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Terry.Bowman@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=ira.weiny@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@kvack.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