From: Christoph Lameter <cl@os.amperecomputing.com>
To: Huang Shijie <shijie@os.amperecomputing.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
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
Subject: Re: [PATCH v2 4/4] arm64: add a new document for the fine-tuning tips
Date: Mon, 2 Dec 2024 11:19:07 -0800 (PST) [thread overview]
Message-ID: <76013b75-dce9-b37c-f2af-9556f14f6301@os.amperecomputing.com> (raw)
In-Reply-To: <20241126085647.4993-5-shijie@os.amperecomputing.com>
On Tue, 26 Nov 2024, Huang Shijie wrote:
> +slab_strict_numa
> +----------------
> +In NUMA, it will provide the local memory allocation by SLUB.
"Slab objects will be placed individually according to memory policies.
Increases object locality which is useful for NUMA systems using SLC
caches"
next prev parent reply other threads:[~2024-12-02 19:19 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 [this message]
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
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=76013b75-dce9-b37c-f2af-9556f14f6301@os.amperecomputing.com \
--to=cl@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.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
all inboxes | Powered by JetHome®