From: Ankur Arora <ankur.a.arora@oracle.com>
To: Ankur Arora <ankur.a.arora@oracle.com>
Cc: "Christoph Lameter (Ampere)" <cl@gentwo.org>,
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,
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 v3 5/5] arm64: barrier: Handle waiting in smp_cond_load_relaxed_timewait()
Date: Mon, 30 Jun 2025 22:55:48 -0700 [thread overview]
Message-ID: <87tt3wqwt7.fsf@oracle.com> (raw)
In-Reply-To: <87h5zxrlce.fsf@oracle.com>
Ankur Arora <ankur.a.arora@oracle.com> writes:
> Christoph Lameter (Ampere) <cl@gentwo.org> writes:
>
>> On Thu, 26 Jun 2025, Ankur Arora wrote:
>>
>>> @@ -222,6 +223,53 @@ do { \
>>> #define __smp_timewait_store(ptr, val) \
>>> __cmpwait_relaxed(ptr, val)
>>>
>>> +/*
>>> + * Redefine ARCH_TIMER_EVT_STREAM_PERIOD_US locally to avoid include hell.
>>> + */
>>> +#define __ARCH_TIMER_EVT_STREAM_PERIOD_US 100UL
>>> +extern bool arch_timer_evtstrm_available(void);
>>> +
>>> +static inline u64 ___smp_cond_spinwait(u64 now, u64 prev, u64 end,
>>> + u32 *spin, bool *wait, u64 slack);
>>> +/*
>>> + * To minimize time spent spinning, we want to allow a large overshoot.
>>> + * So, choose a default slack value of the event-stream period.
>>> + */
>>> +#define SMP_TIMEWAIT_DEFAULT_US __ARCH_TIMER_EVT_STREAM_PERIOD_US
>>> +
>>> +static inline u64 ___smp_cond_timewait(u64 now, u64 prev, u64 end,
>>> + u32 *spin, bool *wait, u64 slack)
>>> +{
>>> + bool wfet = alternative_has_cap_unlikely(ARM64_HAS_WFXT);
>>> + bool wfe, ev = arch_timer_evtstrm_available();
>>
>> An unitialized and initialized variable on the same line. Maybe separate
>> that. Looks confusing and unusual to me.
>
> Yeah, that makes sense. Will fix.
>
>>> + u64 evt_period = __ARCH_TIMER_EVT_STREAM_PERIOD_US;
>>> + u64 remaining = end - now;
>>> +
>>> + if (now >= end)
>>> + return 0;
>>> + /*
>>> + * Use WFE if there's enough slack to get an event-stream wakeup even
>>> + * if we don't come out of the WFE due to natural causes.
>>> + */
>>> + wfe = ev && ((remaining + slack) > evt_period);
>>
>> The line above does not matter for the wfet case and the calculation is
>> ignored. We hope that in the future wfet will be the default case.
>
> My assumption was that the compiler would only evaluate the evt_period
> comparison if the wfet check evaluates false and it does need to check
> if wfe is true or not.
>
> But let me look at the generated code.
So, I was too optimistic. The compiler doesn't do this optimization at
all. I'm guessing that's because of at least two reasons:
The wfet case is unlikely:
bool wfet = alternative_has_cap_unlikely(ARM64_HAS_WFXT);
And, I'm testing for:
if (wfe || wfet)
This last check should have been "if (wfet || wfe)"" since the first
clause is pretty much free.
But even with that fixed, I don't think the compiler will do the right thing.
I could condition the computation on arch_timer_evtstrm_available(), but I
would prefer to keep this code straightforward since it will only be
evaluated infrequently.
But, let me see what I can do.
--
ankur
next prev parent reply other threads:[~2025-07-01 5:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 4:48 [PATCH v3 0/5] barrier: Add smp_cond_load_*_timewait() Ankur Arora
2025-06-27 4:48 ` [PATCH v3 1/5] asm-generic: barrier: Add smp_cond_load_relaxed_timewait() Ankur Arora
2025-08-08 10:51 ` Catalin Marinas
2025-08-11 21:15 ` Ankur Arora
2025-08-13 16:09 ` Catalin Marinas
2025-08-13 16:29 ` Arnd Bergmann
2025-08-13 16:54 ` Christoph Lameter (Ampere)
2025-08-14 13:00 ` Catalin Marinas
2025-08-18 11:51 ` Arnd Bergmann
2025-08-18 18:28 ` Catalin Marinas
2025-08-14 7:30 ` Ankur Arora
2025-08-14 11:39 ` Catalin Marinas
2025-08-17 22:14 ` Ankur Arora
2025-08-18 17:55 ` Catalin Marinas
2025-08-18 19:15 ` Ankur Arora
2025-08-19 10:34 ` Catalin Marinas
2025-06-27 4:48 ` [PATCH v3 2/5] asm-generic: barrier: Handle spin-wait in smp_cond_load_relaxed_timewait() Ankur Arora
2025-06-27 4:48 ` [PATCH v3 3/5] asm-generic: barrier: Add smp_cond_load_acquire_timewait() Ankur Arora
2025-08-08 9:38 ` Catalin Marinas
2025-08-12 5:18 ` Ankur Arora
2025-06-27 4:48 ` [PATCH v3 4/5] arm64: barrier: Support waiting in smp_cond_load_relaxed_timewait() Ankur Arora
2025-06-27 4:48 ` [PATCH v3 5/5] arm64: barrier: Handle " Ankur Arora
2025-06-30 16:33 ` Christoph Lameter (Ampere)
2025-06-30 21:05 ` Ankur Arora
2025-07-01 5:55 ` Ankur Arora [this message]
2025-07-28 19:03 ` [PATCH v3 0/5] barrier: Add smp_cond_load_*_timewait() 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=87tt3wqwt7.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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).