From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, tj@kernel.org,
grygorii.strashko@ti.com, peterz@infradead.org
Subject: Re: How do I increment a per-CPU variable without warning?
Date: Thu, 17 Apr 2014 11:21:06 -0700 [thread overview]
Message-ID: <20140417182106.GP4496@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1404171250190.28585@gentwo.org>
On Thu, Apr 17, 2014 at 12:53:28PM -0500, Christoph Lameter wrote:
> On Thu, 17 Apr 2014, Paul E. McKenney wrote:
>
> > Fair enough! I resent the patch with your Ack to Tejun.
>
> Also note that you may want to use
>
> this_cpu_inc
>
> instead of raw_cpu_inc.
>
> this_cpu_inc will not disable preemption or anything on x86 but just
> create a single instruction using instruction atomicity to avoid the
> preempt on/off sequence.
>
>
> On platforms that cannot emit such an instruction it will fallback to
> disable interrupts for the sequence of instructions that increments the
> value.
>
> With such an approach incrementing the counter should be much safer. If
> the other arch want to avoid irq on/off sequences then they can override
> the fallback to use atomics or whatever the processor architecture permits
> to avoid the overhead of interrupt on / off.
Fair enough, but in this case I don't need it to be safe.
Thanx, Paul
prev parent reply other threads:[~2014-04-17 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 22:17 How do I increment a per-CPU variable without warning? Paul E. McKenney
2014-04-15 22:29 ` Dave Jones
2014-04-15 22:47 ` Paul E. McKenney
2014-04-16 3:54 ` Paul E. McKenney
2014-04-16 5:21 ` Peter Zijlstra
2014-04-16 13:03 ` Paul E. McKenney
2014-04-16 15:12 ` Christoph Lameter
2014-04-16 5:19 ` Peter Zijlstra
2014-04-16 15:08 ` Christoph Lameter
2014-04-16 16:06 ` Paul E. McKenney
2014-04-16 17:12 ` Paul E. McKenney
2014-04-16 18:29 ` Christoph Lameter
2014-04-16 18:47 ` Paul E. McKenney
2014-04-17 17:36 ` Christoph Lameter
2014-04-17 17:46 ` Paul E. McKenney
2014-04-17 17:53 ` Christoph Lameter
2014-04-17 18:21 ` Paul E. McKenney [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=20140417182106.GP4496@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
/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.