All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: cl@linux.com
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org, tj@kernel.org,
	grygorii.strashko@ti.com, peterz@infradead.org
Subject: How do I increment a per-CPU variable without warning?
Date: Tue, 15 Apr 2014 15:17:55 -0700	[thread overview]
Message-ID: <20140415221755.GA27188@linux.vnet.ibm.com> (raw)

Hello, Christoph,

I have a patch that currently uses __this_cpu_inc_return() to increment a
per-CPU variable, but without preemption disabled.  Of course, given that
preemption is enabled, it might well end up picking up one CPU's counter,
adding one to it, then storing the result into some other CPU's counter.
But this is OK, the test can be probabilistic.  And when I run this
against v3.14 and earlier, it works fine.

But now there is 188a81409ff7 (percpu: add preemption checks to
__this_cpu ops), which gives me lots of splats.

My current admittedly crude workaround is as follows:

	static inline bool rcu_should_resched(void)
	{
		int t;

	#ifdef CONFIG_DEBUG_PREEMPT
		preempt_disable();
	#endif /* #ifdef CONFIG_DEBUG_PREEMPT */
		t = __this_cpu_read(rcu_cond_resched_count) + 1;
		if (t < RCU_COND_RESCHED_LIM) {
			__this_cpu_write(rcu_cond_resched_count, t);
	#ifdef CONFIG_DEBUG_PREEMPT
			preempt_enable();
	#endif /* #ifdef CONFIG_DEBUG_PREEMPT */
			return false;
		}
	#ifdef CONFIG_DEBUG_PREEMPT
		preempt_enable();
	#endif /* #ifdef CONFIG_DEBUG_PREEMPT */
		return true;
	}

This is arguably better than the original __this_cpu_read() because it
avoids overflow, but I thought I should check to see if there was some
better way to do this.

							Thanx, Paul


             reply	other threads:[~2014-04-15 22:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 22:17 Paul E. McKenney [this message]
2014-04-15 22:29 ` How do I increment a per-CPU variable without warning? 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

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=20140415221755.GA27188@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.