From: Ankur Arora <ankur.a.arora@oracle.com>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: Ankur Arora <ankur.a.arora@oracle.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, bpf@vger.kernel.org,
arnd@arndb.de, catalin.marinas@arm.com, will@kernel.org,
peterz@infradead.org, akpm@linux-foundation.org,
mark.rutland@arm.com, harisokn@amazon.com, ast@kernel.org,
rafael@kernel.org, daniel.lezcano@linaro.org, memxor@gmail.com,
zhenglifeng1@huawei.com, xueshuai@linux.alibaba.com,
joao.m.martins@oracle.com, boris.ostrovsky@oracle.com,
konrad.wilk@oracle.com
Subject: Re: [PATCH v7 2/7] arm64: barrier: Support smp_cond_load_relaxed_timeout()
Date: Tue, 21 Oct 2025 20:07:31 -0700 [thread overview]
Message-ID: <871pmvws5o.fsf@oracle.com> (raw)
In-Reply-To: <c8be3663-42db-4c8e-cb5c-b7f28aaefc04@gentwo.org>
Christoph Lameter (Ampere) <cl@gentwo.org> writes:
> On Thu, 16 Oct 2025, Ankur Arora wrote:
>
>> +#define SMP_TIMEOUT_POLL_COUNT 1
>
> A way to disable the spinning in the core code and thus arm64 wont spin
> there anymore. Good.
>
> Spinning is bad and a waste of cpu resources. If this is done then I
> would like the arch code to implement the spinning and not the core so
Agreed.
> that there is a motivation for the arch maintainer to
> come up with a way to avoid the spinning at some point.
>
> The patch is ok as is.
>
> Reviewed-by: Christoph Lameter (Ampere) <cl@gentwo.org>
Thanks for all the reviews!
--
ankur
next prev parent reply other threads:[~2025-10-22 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:15 [PATCH v7 0/7] barrier: Add smp_cond_load_*_timeout() Ankur Arora
2025-10-17 6:16 ` [PATCH v7 1/7] asm-generic: barrier: Add smp_cond_load_relaxed_timeout() Ankur Arora
2025-10-21 17:21 ` Christoph Lameter (Ampere)
2025-10-17 6:16 ` [PATCH v7 2/7] arm64: barrier: Support smp_cond_load_relaxed_timeout() Ankur Arora
2025-10-21 17:31 ` Christoph Lameter (Ampere)
2025-10-22 3:07 ` Ankur Arora [this message]
2025-10-17 6:16 ` [PATCH v7 3/7] arm64: rqspinlock: Remove private copy of smp_cond_load_acquire_timewait() Ankur Arora
2025-10-21 17:38 ` Christoph Lameter (Ampere)
2025-10-17 6:16 ` [PATCH v7 4/7] asm-generic: barrier: Add smp_cond_load_acquire_timeout() Ankur Arora
2025-10-17 6:16 ` [PATCH v7 5/7] atomic: Add atomic_cond_read_*_timeout() Ankur Arora
2025-10-21 17:39 ` Christoph Lameter (Ampere)
2025-10-17 6:16 ` [PATCH v7 6/7] rqspinlock: Use smp_cond_load_acquire_timeout() Ankur Arora
2025-10-17 6:16 ` [PATCH v7 7/7] cpuidle/poll_state: Poll via smp_cond_load_relaxed_timeout() Ankur Arora
2025-10-21 17:42 ` Christoph Lameter (Ampere)
2025-10-27 20:06 ` Ankur Arora
2025-10-27 20:13 ` Rafael J. Wysocki
2025-10-28 5:32 ` Ankur Arora
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=871pmvws5o.fsf@oracle.com \
--to=ankur.a.arora@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=daniel.lezcano@linaro.org \
--cc=harisokn@amazon.com \
--cc=joao.m.martins@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=memxor@gmail.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=will@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhenglifeng1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.