On Thu, Mar 02, 2023 at 04:25:08PM -0500, Peter Xu wrote: > On Thu, Mar 02, 2023 at 06:04:25PM -0300, Marcelo Tosatti wrote: > > On Thu, Mar 02, 2023 at 03:53:12PM -0500, Peter Xu wrote: > > > On Thu, Feb 09, 2023 at 12:01:52PM -0300, Marcelo Tosatti wrote: > > > > Goal is to have vmstat_shepherd to transfer from > > > > per-CPU counters to global counters remotely. For this, > > > > an atomic this_cpu_cmpxchg is necessary. > > > > > > > > Following the kernel convention for cmpxchg/cmpxchg_local, > > > > change ARM's this_cpu_cmpxchg_ helpers to be atomic, > > > > and add this_cpu_cmpxchg_local_ helpers which are not atomic. > > > > > > I can follow on the necessity of having the _local version, however two > > > questions below. > > > > > > > > > > > Signed-off-by: Marcelo Tosatti <mtosatti@xxxxxxxxxx> > > > > > > > > Index: linux-vmstat-remote/arch/arm64/include/asm/percpu.h > > > > =================================================================== > > > > --- linux-vmstat-remote.orig/arch/arm64/include/asm/percpu.h > > > > +++ linux-vmstat-remote/arch/arm64/include/asm/percpu.h > > > > @@ -232,13 +232,23 @@ PERCPU_RET_OP(add, add, ldadd) > > > > _pcp_protect_return(xchg_relaxed, pcp, val) > > > > > > > > #define this_cpu_cmpxchg_1(pcp, o, n) \ > > > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > > > #define this_cpu_cmpxchg_2(pcp, o, n) \ > > > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > > > #define this_cpu_cmpxchg_4(pcp, o, n) \ > > > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > > > #define this_cpu_cmpxchg_8(pcp, o, n) \ > > > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > > > > > This makes this_cpu_cmpxchg_*() not only non-local, but also (especially > > > for arm64) memory barrier implications since cmpxchg() has a strong memory > > > barrier, while the old this_cpu_cmpxchg*() doesn't have, afaiu. > > > > > > Maybe it's not a big deal if the audience of this helper is still limited > > > (e.g. we can add memory barriers if we don't want strict ordering > > > implication), but just to check with you on whether it's intended, and if > > > so whether it may worth some comments. > > > > It happens that on ARM-64 cmpxchg_local == cmpxchg_relaxed. > > > > See cf10b79a7d88edc689479af989b3a88e9adf07ff. > > This is more or less a comment in general, rather than for arm only. > > Fundamentally starting from this patch it's redefining this_cpu_cmpxchg(). > What I meant is whether we should define it properly then implement the > arch patches with what is defined. > > We're adding non-local semantics into it, which is obvious to me. Which match the cmpxchg() function semantics. > We're (silently, in this patch for aarch64) adding memory barrier semantics > too, this is not obvious to me on whether all archs should implement this > api the same way. Documentation/atomic_t.txt says that _relaxed means "no barriers". So i'd assume: cmpxchg_relaxed: no additional barriers cmpxchg_local: only guarantees atomicity to wrt local CPU. cmpxchg: atomic in SMP context. https://lore.kernel.org/linux-arm-kernel/20180505103550.s7xsnto7tgppkmle@xxxxxxxxx/#r There seems to be a lack of clarity in documentation. > It will make a difference IMHO when the helpers are used in any other code > clips, because IIUC proper definition of memory barrier implications will > decide whether the callers need explicit barriers when ordering is required. Trying to limit the scope of changes to solve the problem at hand. More specifically what this patch does is: 1) Add this_cpu_cmpxchg_local, uses arch cmpxchg_local implementation to back it. 2) Add this_cpu_cmpxchg, uses arch cmpxchg implementation to back it. Note that now becomes consistent with cmpxchg and cmpxchg_local semantics. > > This patchset maintains the current behaviour > > of this_cpu_cmpxch (for this_cpu_cmpxch_local), which was: > > > > #define this_cpu_cmpxchg_1(pcp, o, n) \ > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > #define this_cpu_cmpxchg_2(pcp, o, n) \ > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > #define this_cpu_cmpxchg_4(pcp, o, n) \ > > - _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > #define this_cpu_cmpxchg_8(pcp, o, n) \ > > + _pcp_protect_return(cmpxchg, pcp, o, n) > > > > > > + > > > > +#define this_cpu_cmpxchg_local_1(pcp, o, n) \ > > > > _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > +#define this_cpu_cmpxchg_local_2(pcp, o, n) \ > > > > + _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > +#define this_cpu_cmpxchg_local_4(pcp, o, n) \ > > > > + _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > +#define this_cpu_cmpxchg_local_8(pcp, o, n) \ > > > > + _pcp_protect_return(cmpxchg_relaxed, pcp, o, n) > > > > > > I think cmpxchg_relaxed()==cmpxchg_local() here for aarch64, however should > > > we still use cmpxchg_local() to pair with this_cpu_cmpxchg_local_*()? > > > > Since cmpxchg_local = cmpxchg_relaxed, seems like this is not necessary. > > > > > Nothing about your patch along since it was the same before, but I'm > > > wondering whether this is a good time to switchover. > > > > I would say that another patch is more appropriate to change this, > > if desired. > > Sure on this one. Thanks, > > -- > Peter Xu > >
