From: Shijie Huang <shijie@amperemail.onmicrosoft.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
Huang Shijie <shijie@os.amperecomputing.com>,
catalin.marinas@arm.com, will@kernel.org
Cc: patches@amperecomputing.com, paulmck@kernel.org,
akpm@linux-foundation.org, thuth@redhat.com, rostedt@goodmis.org,
xiongwei.song@windriver.com, ardb@kernel.org,
steven.price@arm.com, suzuki.poulose@arm.com,
mark.rutland@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, cl@os.amperecomputing.com
Subject: Re: [PATCH v2 4/4] arm64: add a new document for the fine-tuning tips
Date: Fri, 6 Dec 2024 14:14:26 +0800 [thread overview]
Message-ID: <e7cbafd4-506b-4e26-ad88-e1afba06e972@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <e48df345-0946-4b34-a463-e89aa89680f9@arm.com>
On 2024/12/6 11:56, Anshuman Khandual wrote:
> On 11/26/24 14:26, Huang Shijie wrote:
>> Put some fine-tuning tips in this file:
>> 1.) rodata=noalias
>> 2.) slab_strict_numa
>> 3.) CONFIG_SCHED_CLUSTER
>>
>> We can add more tips in future.
>>
>> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
>> ---
>> Documentation/arch/arm64/fine-tuning-tips.rst | 23 +++++++++++++++++++
>> Documentation/arch/arm64/index.rst | 1 +
>> 2 files changed, 24 insertions(+)
>> create mode 100644 Documentation/arch/arm64/fine-tuning-tips.rst
>>
>> diff --git a/Documentation/arch/arm64/fine-tuning-tips.rst b/Documentation/arch/arm64/fine-tuning-tips.rst
>> new file mode 100644
>> index 000000000000..70ef1cef92fb
>> --- /dev/null
>> +++ b/Documentation/arch/arm64/fine-tuning-tips.rst
>> @@ -0,0 +1,23 @@
>> +.. SPDX-License-Identifier: GPL-2.0
>> +
>> +================
>> +fine-tuning tips
>> +================
>> +
>> +This file contains some fine-tuning tips for arm64 machines.
>> +These tips do not gurantee that you can get better performance,
>> +but you can try them with your workload.
>> +
>> +rodata=noalias
>> +----------------
>> +It can provide us more block mappings and contiguous hits
>> +to map the linear region which minimizes the TLB footprint.
>> +
>> +slab_strict_numa
>> +----------------
>> +In NUMA, it will provide the local memory allocation by SLUB.
>> +
>> +CONFIG_SCHED_CLUSTER
>> +----------------
>> +Some arm64 machines have cpu core cluster, enable it may
>> +helps you get better performance.
>> diff --git a/Documentation/arch/arm64/index.rst b/Documentation/arch/arm64/index.rst
>> index 6a012c98bdcd..36d1ef09bd71 100644
>> --- a/Documentation/arch/arm64/index.rst
>> +++ b/Documentation/arch/arm64/index.rst
>> @@ -16,6 +16,7 @@ ARM64 Architecture
>> cpu-feature-registers
>> cpu-hotplug
>> elf_hwcaps
>> + fine-tuning-tips
>> gcs
>> hugetlbpage
>> kdump
> Although the idea for such a file makes sense, to help system admins
> tune the kernel command line for required behaviour, I am concerned
This file also contains the CONFIG_SCHED_CLUSTER which is not a kernel
command line.
> about the overall structure and scope for such a document. Should it
> contain tips regarding all the subsystems on the platform, till what
> extent these details should be described in there and then there are
> so many aspects for a required behaviour etc ?
My original thought is to let this file contains the tips only works in
arm64.
All the tips which _may_ make the arm64 machines get better performance
can be
recorded here.
Then the arm64 kernel engineers(the newbies) can follow this file, and
ramp up
quickly.
>
> Besides maintaining such a document might also be very difficult as
> well given how implementations will change over time thus requiring
> different tuning etc. Hence kernel source might not be a place for
> such a document.
okay. If the kernel source is not the right place, I can remove this
patch in next version.
Thanks
Huang Shijie
prev parent reply other threads:[~2024-12-06 6:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 8:56 [PATCH v2 0/4] arm64: refactor the rodata=xxx Huang Shijie
2024-11-26 8:56 ` [PATCH v2 1/4] arm64: make rodata=on behaviour be the original rodata=full Huang Shijie
2024-12-06 4:21 ` Anshuman Khandual
2024-11-26 8:56 ` [PATCH v2 2/4] arm64: remove CONFIG_RODATA_FULL_DEFAULT_ENABLED Huang Shijie
2024-12-06 4:40 ` Anshuman Khandual
2024-11-26 8:56 ` [PATCH v2 3/4] arm64: introduce rodata=noalias Huang Shijie
2024-12-06 4:29 ` Anshuman Khandual
2024-12-06 5:50 ` Shijie Huang
2024-11-26 8:56 ` [PATCH v2 4/4] arm64: add a new document for the fine-tuning tips Huang Shijie
2024-12-02 19:19 ` Christoph Lameter
2024-12-06 3:23 ` [PATCH v2 4/4 fix] " Huang Shijie
2024-12-06 3:56 ` [PATCH v2 4/4] " Anshuman Khandual
2024-12-06 6:14 ` Shijie Huang [this message]
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=e7cbafd4-506b-4e26-ad88-e1afba06e972@amperemail.onmicrosoft.com \
--to=shijie@amperemail.onmicrosoft.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@os.amperecomputing.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=patches@amperecomputing.com \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shijie@os.amperecomputing.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thuth@redhat.com \
--cc=will@kernel.org \
--cc=xiongwei.song@windriver.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