From: Ira Weiny <ira.weiny@intel.com>
To: Gregory Price <gourry@gourry.net>, <linux-mm@kvack.org>,
<linux-acpi@vger.kernel.org>
Cc: <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>, <david@redhat.com>,
<osalvador@suse.de>, <gregkh@linuxfoundation.org>,
<akpm@linux-foundation.org>, <dan.j.williams@intel.com>,
<Jonathan.Cameron@huawei.com>, <alison.schofield@intel.com>,
<rrichter@amd.com>, <rppt@kernel.org>, <gourry@gourry.net>,
<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: [RESEND v7 1/3] memory: implement memory_block_advise/probe_max_size
Date: Mon, 13 Jan 2025 14:51:30 -0600 [thread overview]
Message-ID: <67857cd2524a9_1863f3294d8@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20250113174439.1965168-2-gourry@gourry.net>
Gregory Price wrote:
> Hotplug memory sources may have opinions on what the memblock size
> should be - usually for alignment purposes. For example, CXL memory
> extents can be 256MB with a matching alignment. If this size/alignment
> is smaller than the block size, it can result in stranded capacity.
>
> Implement memory_block_advise_max_size for use prior to allocator init,
> for software to advise the system on the max block size.
>
> Implement memory_block_probe_max_size for use by arch init code to
> calculate the best block size. Use of advice is architecture defined.
>
> The probe value can never change after first probe. Calls to advise
> after probe will return -EBUSY to aid debugging.
>
> On systems without hotplug, always return -ENODEV and 0 respectively.
>
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Acked-by: David Hildenbrand <david@redhat.com>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
> Tested-by: Fan Ni <fan.ni@samsung.com>
> ---
[snip]
> +int __init memory_block_advise_max_size(unsigned long size)
> +{
> + if (!size || !is_power_of_2(size))
> + return -EINVAL;
> +
> + if (memory_block_advised_size_queried)
> + return -EBUSY;
> +
> + if (memory_block_advised_size) {
> + memory_block_advised_size = min(memory_block_advised_size,
> + size);
> + } else {
> + memory_block_advised_size = size;
> + }
NIT: Style: single statements don't need '{}'
Other than that it looks ok.
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
[snip]
next prev parent reply other threads:[~2025-01-13 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 17:44 [RESEND v7 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2025-01-13 17:44 ` [RESEND v7 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2025-01-13 20:51 ` Ira Weiny [this message]
2025-01-13 17:44 ` [RESEND v7 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2025-01-13 20:56 ` Ira Weiny
2025-01-13 17:44 ` [RESEND v7 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2025-01-13 19:10 ` Rafael J. Wysocki
2025-01-13 20:59 ` Ira Weiny
2025-01-13 21:06 ` Gregory Price
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=67857cd2524a9_1863f3294d8@iweiny-mobl.notmuch \
--to=ira.weiny@intel.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=david@redhat.com \
--cc=fan.ni@samsung.com \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=haibo1.xu@intel.com \
--cc=hpa@zytor.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