From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, catalin.marinas@arm.com,
linux-mm@kvack.org, steven.price@arm.com,
anshuman.khandual@arm.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
guojian@oppo.com, ying.huang@intel.com, hughd@google.com,
hanchuanhua@oppo.com, v-songbaohua@oppo.com, hannes@cmpxchg.org,
minchan@kernel.org, zhangshiming@oppo.com,
linux-kernel@vger.kernel.org, aarcange@redhat.com,
shy828301@gmail.com
Subject: Re: [PATCH v4] arm64: enable THP_SWAP for arm64
Date: Wed, 20 Jul 2022 11:15:09 +0100 [thread overview]
Message-ID: <165831076076.3414765.4205578904635194044.b4-ty@kernel.org> (raw)
In-Reply-To: <20220720093737.133375-1-21cnbao@gmail.com>
On Wed, 20 Jul 2022 21:37:37 +1200, Barry Song wrote:
> From: Barry Song <v-songbaohua@oppo.com>
>
> THP_SWAP has been proven to improve the swap throughput significantly
> on x86_64 according to commit bd4c82c22c367e ("mm, THP, swap: delay
> splitting THP after swapped out").
> As long as arm64 uses 4K page size, it is quite similar with x86_64
> by having 2MB PMD THP. THP_SWAP is architecture-independent, thus,
> enabling it on arm64 will benefit arm64 as well.
> A corner case is that MTE has an assumption that only base pages
> can be swapped. We won't enable THP_SWAP for ARM64 hardware with
> MTE support until MTE is reworked to coexist with THP_SWAP.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: enable THP_SWAP for arm64
https://git.kernel.org/arm64/c/d0637c505f8a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-07-20 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 9:37 Barry Song
2022-07-20 10:15 ` Will Deacon [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=165831076076.3414765.4205578904635194044.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=21cnbao@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=guojian@oppo.com \
--cc=hanchuanhua@oppo.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=shy828301@gmail.com \
--cc=steven.price@arm.com \
--cc=v-songbaohua@oppo.com \
--cc=ying.huang@intel.com \
--cc=zhangshiming@oppo.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