linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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@vger.kernel.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 v4 1/3] memory: implement memory_block_advise/probe_max_size
Date: Wed, 30 Oct 2024 17:35:18 +0100	[thread overview]
Message-ID: <c99e0eca-49f6-4167-ad2b-d4168193ea7e@redhat.com> (raw)
In-Reply-To: <ZyJJ5Pvfj4Spcyo7@PC2K9PVX.TheFacebook.com>

On 30.10.24 15:59, Gregory Price wrote:
> On Wed, Oct 30, 2024 at 11:25:33AM +0100, David Hildenbrand wrote:
>> On 29.10.24 21:20, 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>
>>> ---
>>>    drivers/base/memory.c  | 48 ++++++++++++++++++++++++++++++++++++++++++
>>>    include/linux/memory.h | 10 +++++++++
>>>    2 files changed, 58 insertions(+)
>>>
>>> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
>>> index 67858eeb92ed..099a972c52dc 100644
>>> --- a/drivers/base/memory.c
>>> +++ b/drivers/base/memory.c
>>> @@ -110,6 +110,54 @@ static void memory_block_release(struct device *dev)
>>>    	kfree(mem);
>>>    }
>>> +/**
>>> + * memory_block_advise_max_size() - advise memory hotplug on the max suggested
>>> + *				    block size, usually for alignment.
>>> + * @size: suggestion for maximum block size. must be aligned on power of 2.
>>> + *
>>> + * Early boot software (pre-allocator init) may advise archs on the max block
>>> + * size. This value can only decrease after initialization, as the intent is
>>> + * to identify the largest supported alignment for all sources.
>>> + *
>>> + * Use of this value is arch-defined, as is min/max block size.
>>> + *
>>> + * Return: 0 on success
>>> + *	   -EINVAL if size is 0 or not pow2 aligned
>>> + *	   -EBUSY if value has already been probed
>>> + */
>>> +static size_t memory_block_advised_sz;
>>
>> Nit: if everything is called "size", call this "size" as well.
>>
> 
> Mostly shortened here because
> 
> 	if (memory_block_advised_sz)
> 		memory_block_advised_size = min(size, memory_block_advised_size);
> 
> is over 80 characters lol.  Happy to change if you have strong feelings.

Feel free to exceed 80 chars if there is good reason to -- like in this 
case. checkpatch.pl nowadays complains if you exceed 100 chars.

No strong feelings, making it consistent in some way would be "nice" ;)

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-10-30 16:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 20:20 [PATCH v4 0/3] memory,x86,acpi: hotplug memory alignment advisement Gregory Price
2024-10-29 20:20 ` [PATCH v4 1/3] memory: implement memory_block_advise/probe_max_size Gregory Price
2024-10-30 10:25   ` David Hildenbrand
2024-10-30 14:59     ` Gregory Price
2024-10-30 16:35       ` David Hildenbrand [this message]
2024-10-31 14:31   ` Mike Rapoport
2024-10-31 16:23     ` Gregory Price
2024-10-29 20:20 ` [PATCH v4 2/3] x86: probe memory block size advisement value during mm init Gregory Price
2024-10-30 10:26   ` David Hildenbrand
2024-10-29 20:20 ` [PATCH v4 3/3] acpi,srat: give memory block size advice based on CFMWS alignment Gregory Price
2024-10-30 10:40   ` David Hildenbrand
2024-10-30 15:01     ` Gregory Price
2024-10-30 15:25     ` 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=c99e0eca-49f6-4167-ad2b-d4168193ea7e@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@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