[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43b24caf-2ade-e229-21f4-8c01a47f37ed@gentwo.org>
Date: Mon, 5 Aug 2024 16:09:58 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Ankur Arora <ankur.a.arora@...cle.com>
cc: linux-pm@...r.kernel.org, kvm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
catalin.marinas@....com, will@...nel.org, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, pbonzini@...hat.com, wanpengli@...cent.com,
vkuznets@...hat.com, rafael@...nel.org, daniel.lezcano@...aro.org,
peterz@...radead.org, arnd@...db.de, lenb@...nel.org, mark.rutland@....com,
harisokn@...zon.com, mtosatti@...hat.com, sudeep.holla@....com,
misono.tomohiro@...itsu.com, joao.m.martins@...cle.com,
boris.ostrovsky@...cle.com, konrad.wilk@...cle.com
Subject: Re: [PATCH v6 02/10] cpuidle: rename ARCH_HAS_CPU_RELAX to
ARCH_HAS_OPTIMIZED_POLL
On Fri, 26 Jul 2024, Ankur Arora wrote:
> However, recent changes in poll_idle() mean that a higher level
> primitive -- smp_cond_load_relaxed() is used for polling. This would
> in-turn use cpu_relax() or an architecture specific implementation.
Maybe explain here that smp_cond_load_relaxed will potentially wait for
important events such as a cacheline changing. Thereby making the busy
poll unnecessary and optimizing power use.
Powered by blists - more mailing lists