linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>,
	linux-arch@vger.kernel.org,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Tejun Heo <tj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH RFC] Introduce atomic and per-cpu add-max and sub-min operations
Date: Mon, 15 Feb 2016 15:14:07 +0100	[thread overview]
Message-ID: <20160215141407.GE6357@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160215105028.GB1748@arm.com>

On Mon, Feb 15, 2016 at 10:50:29AM +0000, Will Deacon wrote:
> Adding Peter and Paul,
> 
> On Sun, Feb 14, 2016 at 12:09:00PM +0300, Konstantin Khlebnikov wrote:
> > bool atomic_add_max(atomic_t *var, int add, int max);
> > bool atomic_sub_min(atomic_t *var, int sub, int min);
> 
> What are the memory-ordering requirements for these? Do you also want
> relaxed/acquire/release versions for the use-cases you outline?
> 
> One observation is that you provide no ordering guarantees if the
> comparison fails, which is fine if that's what you want, but we should
> probably write that down like we do for cmpxchg.
> 
> > bool this_cpu_add_max(var, add, max);
> > bool this_cpu_sub_min(var, sub, min);
> > 
> > They add/subtract only if result will be not bigger than max/lower that min.
> > Returns true if operation was done and false otherwise.
> > 
> > Inside they check that (add <= max - var) and (sub <= var - min). Signed
> > operations work if all possible values fits into range which length fits
> > into non-negative range of that type: 0..INT_MAX, INT_MIN+1..0, -1000..1000.
> > Unsigned operations work if value always in valid range: min <= var <= max.
> > Char and short automatically casts to int, they never overflows.
> > 
> > Patch adds the same for atomic_long_t, atomic64_t, local_t, local64_t.
> > And unsigned variants: atomic_u32_add_max atomic_u32_sub_min for atomic_t,
> > atomic_u64_add_max atomic_u64_sub_min for atomic64_t.
> > 
> > Patch comes with test which hopefully covers all possible cornercases,
> > see CONFIG_ATOMIC64_SELFTEST and CONFIG_PERCPU_TEST.
> > 
> > All this allows to build any kind of counter in several lines:
> 
> Do you have another patch converting people over to these new atomics?

The Changelog completely lacks a why. Why do we want this?

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2016-02-15 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  9:09 Konstantin Khlebnikov
2016-02-14 16:51 ` Tejun Heo
2016-02-14 17:37   ` Konstantin Khlebnikov
2016-02-16 16:10     ` Christoph Lameter
2016-02-15 10:50 ` Will Deacon
2016-02-15 11:13   ` Konstantin Khlebnikov
2016-02-15 14:14   ` Peter Zijlstra [this message]

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=20160215141407.GE6357@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=koct9i@gmail.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tj@kernel.org \
    --cc=will.deacon@arm.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