From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Carl Worth <carl@os.amperecomputing.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Taehyun Noh <taehyun@utexas.edu>
Subject: Re: [PATCH v2 0/2] arm64: mte: Improve performance by explicitly disabling unwanted tag checking
Date: Tue, 27 Jan 2026 11:39:09 +0000 [thread overview]
Message-ID: <176951239741.2185302.14847899262435443119.b4-ty@kernel.org> (raw)
In-Reply-To: <20251030-mte-tighten-tco-v2-0-e259dda9d5b3@os.amperecomputing.com>
On Thu, 15 Jan 2026 15:07:16 -0800, Carl Worth wrote:
> [Thanks to Taehyun Noh from UT Austin for originally reporting this
> bug. In this cover letter, "we" refers to a collaborative effort
> between indiviuals at both Ampere Computing and UT Austin.]
>
> We measured severe performance overhead (25-50%) when enabling
> userspace MTE and running memcached on an AmpereOne machine, (detailed
> benchmark results are provided below).
>
> [...]
Applied TCMA1 patch to arm64 (for-next/cpufeature), thanks!
[2/2] arm64: mte: Set TCMA1 whenever MTE is present in the kernel
https://git.kernel.org/arm64/c/a4e5927115f3
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-01-27 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 23:07 Carl Worth
2026-01-15 23:07 ` [PATCH v2 1/2] arm64: mte: Clarify kernel MTE policy and manipulation of TCO Carl Worth
2026-01-19 18:17 ` Catalin Marinas
2026-01-20 19:44 ` Taehyun Noh
2026-01-15 23:07 ` [PATCH v2 2/2] arm64: mte: Set TCMA1 whenever MTE is present in the kernel Carl Worth
2026-01-19 17:57 ` Catalin Marinas
2026-01-22 10:23 ` Usama Anjum
2026-01-22 11:49 ` Catalin Marinas
2026-01-27 11:39 ` 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=176951239741.2185302.14847899262435443119.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=carl@os.amperecomputing.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taehyun@utexas.edu \
/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®