From: Dave Hansen <dave.hansen@intel•com>
To: Uros Bizjak <ubizjak@gmail•com>,
linux-alpha@vger•kernel.org, loongarch@lists•linux.dev,
linux-mips@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
x86@kernel•org, linux-arch@vger•kernel.org,
linux-perf-users@vger•kernel.org, linux-kernel@vger•kernel.org
Cc: Mark Rutland <mark.rutland@arm•com>,
Ian Rogers <irogers@google•com>,
Peter Zijlstra <peterz@infradead•org>,
Dave Hansen <dave.hansen@linux•intel.com>,
Jiaxun Yang <jiaxun.yang@flygoat•com>,
"H. Peter Anvin" <hpa@zytor•com>, WANG Xuerui <kernel@xen0n•name>,
Will Deacon <will@kernel•org>, Jun Yi <yijun@loongson•cn>,
Huacai Chen <chenhuacai@kernel•org>,
Alexander Shishkin <alexander.shishkin@linux•intel.com>,
Ingo Molnar <mingo@redhat•com>, Matt Turner <mattst88@gmail•com>,
Arnd Bergmann <arnd@arndb•de>, Boqun Feng <boqun.feng@gmail•com>,
Richard Henderson <richard.henderson@linaro•org>,
Nicholas Piggin <npiggin@gmail•com>,
Ivan Kokshaysky <ink@jurassic•park.msu.ru>,
Arnaldo Carvalho de Melo <acme@kernel•org>,
Namhyung Kim <namhyung@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
Thomas Bogendoerfer <tsbogend@alpha•franken.de>,
Jiri Olsa <jolsa@kernel•org>, Borislav Petkov <bp@alien8•de>
Subject: Re: [PATCH v2 0/5] locking: Introduce local{,64}_try_cmpxchg
Date: Wed, 5 Apr 2023 09:37:04 -0700 [thread overview]
Message-ID: <7360ffd2-a5aa-1373-8309-93e71ff36cbb@intel.com> (raw)
In-Reply-To: <20230405141710.3551-1-ubizjak@gmail.com>
On 4/5/23 07:17, Uros Bizjak wrote:
> Add generic and target specific support for local{,64}_try_cmpxchg
> and wire up support for all targets that use local_t infrastructure.
I feel like I'm missing some context.
What are the actual end user visible effects of this series? Is there a
measurable decrease in perf overhead? Why go to all this trouble for
perf? Who else will use local_try_cmpxchg()?
I'm all for improving things, and perf is an important user. But, if
the goal here is improving performance, it would be nice to see at least
a stab at quantifying the performance delta.
next prev parent reply other threads:[~2023-04-05 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 14:17 [PATCH v2 0/5] locking: Introduce local{,64}_try_cmpxchg Uros Bizjak
2023-04-05 14:17 ` [PATCH v2 1/5] locking/atomic: Add generic try_cmpxchg{,64}_local support Uros Bizjak
2023-04-11 11:10 ` Mark Rutland
2023-04-05 14:17 ` [PATCH v2 2/5] locking/generic: Wire up local{,64}_try_cmpxchg Uros Bizjak
2023-04-11 11:13 ` Mark Rutland
2023-04-05 14:17 ` [PATCH v2 3/5] locking/arch: Wire up local_try_cmpxchg Uros Bizjak
2023-04-12 11:32 ` Peter Zijlstra
2023-04-12 13:37 ` Uros Bizjak
2023-04-12 13:40 ` Peter Zijlstra
2023-05-17 7:41 ` Charlemagne Lasse
2023-04-05 14:17 ` [PATCH v2 4/5] locking/x86: Define arch_try_cmpxchg_local Uros Bizjak
2023-04-05 14:17 ` [PATCH v2 5/5] events: Illustrate the transition to local{,64}_try_cmpxchg Uros Bizjak
2023-04-05 16:37 ` Dave Hansen [this message]
2023-04-05 18:53 ` [PATCH v2 0/5] locking: Introduce local{,64}_try_cmpxchg Uros Bizjak
2023-04-06 8:25 ` David Laight
2023-04-06 8:38 ` Uros Bizjak
2023-04-06 9:01 ` David Laight
2023-04-11 11:35 ` Mark Rutland
2023-04-11 13:43 ` Dave Hansen
2023-04-11 21:34 ` David Laight
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=7360ffd2-a5aa-1373-8309-93e71ff36cbb@intel.com \
--to=dave.hansen@intel$(echo .)com \
--cc=acme@kernel$(echo .)org \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=arnd@arndb$(echo .)de \
--cc=boqun.feng@gmail$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=chenhuacai@kernel$(echo .)org \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=hpa@zytor$(echo .)com \
--cc=ink@jurassic$(echo .)park.msu.ru \
--cc=irogers@google$(echo .)com \
--cc=jiaxun.yang@flygoat$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kernel@xen0n$(echo .)name \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux-perf-users@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=loongarch@lists$(echo .)linux.dev \
--cc=mark.rutland@arm$(echo .)com \
--cc=mattst88@gmail$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=namhyung@kernel$(echo .)org \
--cc=npiggin@gmail$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=richard.henderson@linaro$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=tsbogend@alpha$(echo .)franken.de \
--cc=ubizjak@gmail$(echo .)com \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
--cc=yijun@loongson$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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