From: Yang Shi <yang@os.amperecomputing.com>
To: catalin.marinas@arm.com, will@kernel.org
Cc: cl@gentwo.org, scott@os.amperecomputing.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 PATCH 0/2] arm64: support FEAT_BBM level 2 and large block mapping when rodata=full
Date: Wed, 22 Jan 2025 10:04:41 -0800 [thread overview]
Message-ID: <77f40fc5-8bb0-42a6-9e34-c56f3407eef1@os.amperecomputing.com> (raw)
In-Reply-To: <20250103011822.1257189-1-yang@os.amperecomputing.com>
Ping...
Per the prior discussion, the BBM level 2 feature is advertised via a
allow list in this version. Any more comment on the implementation and
patch 2? I expected there should be more comments on patch 2.
Thanks,
Yang
On 1/2/25 5:17 PM, Yang Shi wrote:
> When rodata=full kernel linear mapping is mapped by PTE due to arm's
> break-before-make rule.
>
> This resulted in a couple of problems:
> - performance degradation
> - more TLB pressure
> - memory waste for kernel page table
>
> There are some workarounds to mitigate the problems, for example, using
> rodata=on, but this compromises the security measurement.
>
> With FEAT_BBM level 2 support, splitting large block page table to
> smaller ones doesn't need to make the page table entry invalid anymore.
> This allows kernel split large block mapping on the fly.
>
> Add kernel page table split support and use large block mapping by
> default when FEAT_BBM level 2 is supported for rodata=full. When
> changing permissions for kernel linear mapping, the page table will be
> split to PTE level.
>
> The machine without FEAT_BBM level 2 will fallback to have kernel linear
> mapping PTE-mapped when rodata=full.
>
> With this we saw significant performance boost with some benchmarks with
> keeping rodata=full security protection in the mean time.
>
> The test was done on AmpereOne machine (192 cores, 1P) with 256GB memory and
> 4K page size + 48 bit VA.
>
> Function test (4K/16K/64K page size)
> - Kernel boot. Kernel needs change kernel linear mapping permission at
> boot stage, if the patch didn't work, kernel typically didn't boot.
> - Module stress from stress-ng. Kernel module load change permission for
> module sections.
> - A test kernel module which allocates 80% of total memory via vmalloc(),
> then change the vmalloc area permission to RO, then change it back
> before vfree(). Then launch a VM which consumes almost all physical
> memory.
> - VM with the patchset applied in guest kernel too.
> - Kernel build in VM with patched guest kernel.
>
> Memory consumption
> Before:
> MemTotal: 258988984 kB
> MemFree: 254821700 kB
>
> After:
> MemTotal: 259505132 kB
> MemFree: 255410264 kB
>
> Around 500MB more memory are free to use. The larger the machine, the
> more memory saved.
>
> Performance benchmarking
> * Memcached
> We saw performance degradation when running Memcached benchmark with
> rodata=full vs rodata=on. Our profiling pointed to kernel TLB pressure.
> With this patchset we saw ops/sec is increased by around 3.5%, P99
> latency is reduced by around 9.6%.
> The gain mainly came from reduced kernel TLB misses. The kernel TLB
> MPKI is reduced by 28.5%.
>
> The benchmark data is now on par with rodata=on too.
>
> * Disk encryption (dm-crypt) benchmark
> Ran fio benchmark with the below command on a 128G ramdisk (ext4) with disk
> encryption (by dm-crypt).
> fio --directory=/data --random_generator=lfsr --norandommap --randrepeat 1 \
> --status-interval=999 --rw=write --bs=4k --loops=1 --ioengine=sync \
> --iodepth=1 --numjobs=1 --fsync_on_close=1 --group_reporting --thread \
> --name=iops-test-job --eta-newline=1 --size 100G
>
> The IOPS is increased by 90% - 150% (the variance is high, but the worst
> number of good case is around 90% more than the best number of bad case).
> The bandwidth is increased and the avg clat is reduced proportionally.
>
> * Sequential file read
> Read 100G file sequentially on XFS (xfs_io read with page cache populated).
> The bandwidth is increased by 150%.
>
> RFC v2:
> * Used allowlist to advertise BBM lv2 on the CPUs which can handle TLB
> conflict gracefully per Will Deacon
> * Rebased onto v6.13-rc5
>
> RFC v1: https://lore.kernel.org/lkml/20241118181711.962576-1-yang@os.amperecomputing.com/
>
> Yang Shi (2):
> arm64: cpufeature: detect FEAT_BBM level 2
> arm64: mm: support large block mapping when rodata=full
>
> arch/arm64/include/asm/cpufeature.h | 19 ++++++++++++
> arch/arm64/include/asm/pgtable.h | 7 ++++-
> arch/arm64/kernel/cpufeature.c | 11 +++++++
> arch/arm64/mm/mmu.c | 32 ++++++++++++++++++--
> arch/arm64/mm/pageattr.c | 173 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
> arch/arm64/tools/cpucaps | 1 +
> 6 files changed, 234 insertions(+), 9 deletions(-)
next prev parent reply other threads:[~2025-01-22 18:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 1:17 Yang Shi
2025-01-03 1:17 ` [v2 PATCH 1/2] arm64: cpufeature: detect FEAT_BBM level 2 Yang Shi
2025-02-11 11:55 ` Ryan Roberts
2025-02-13 21:14 ` Yang Shi
2025-02-18 11:17 ` Ryan Roberts
2025-02-20 0:19 ` Yang Shi
2025-01-03 1:17 ` [v2 PATCH 2/2] arm64: mm: support large block mapping when rodata=full Yang Shi
2025-02-11 12:58 ` Ryan Roberts
2025-02-13 21:18 ` Yang Shi
2025-02-18 13:28 ` Ryan Roberts
2025-02-20 1:11 ` Yang Shi
2025-01-22 18:04 ` Yang Shi [this message]
[not found] ` <022c4799-bf0e-44d4-b657-d6af29a9a31d@arm.com>
2025-02-11 11:36 ` [RFC v2 PATCH 0/2] arm64: support FEAT_BBM level 2 and " Ryan Roberts
2025-02-13 21:27 ` Yang Shi
2025-02-18 11:58 ` Ryan Roberts
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=77f40fc5-8bb0-42a6-9e34-c56f3407eef1@os.amperecomputing.com \
--to=yang@os.amperecomputing.com \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@os.amperecomputing.com \
--cc=will@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
all inboxes | Powered by JetHome®