From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
rostedt@goodmis.org, Valdis.Kletnieks@vt.edu,
dhowells@redhat.com, eric.dumazet@gmail.com, darren@dvhart.com,
fweisbec@gmail.com, patches@linaro.org,
"Paul E. McKenney" <paul.mckenney@linaro.org>
Subject: Re: [PATCH RFC tip/core/rcu 3/4] rcu: Make RCU_FAST_NO_HZ account for pauses out of idle
Date: Thu, 26 Apr 2012 15:00:42 +0200 [thread overview]
Message-ID: <1335445242.13683.19.camel@twins> (raw)
In-Reply-To: <1335197761-6577-3-git-send-email-paulmck@linux.vnet.ibm.com>
On Mon, 2012-04-23 at 09:16 -0700, Paul E. McKenney wrote:
> static DEFINE_PER_CPU(int, rcu_dyntick_drain);
> static DEFINE_PER_CPU(unsigned long, rcu_dyntick_holdoff);
> static DEFINE_PER_CPU(struct timer_list, rcu_idle_gp_timer);
> +static DEFINE_PER_CPU(unsigned long, rcu_idle_gp_timer_expires);
> +static DEFINE_PER_CPU(bool, rcu_idle_first_pass);
> +static DEFINE_PER_CPU(unsigned long, rcu_nonlazy_posted);
> +static DEFINE_PER_CPU(unsigned long, rcu_nonlazy_posted_snap);
Wouldn't that all be prettier if it were in a struct of sorts?
struct rcu_dyntick {
int drain;
unsigned long holdoff;
struct timer_list gp_timer;
unsigned long gp_timer_expires;
bool first_pass;
unsigned long posted;
unsigned long posted_snap;
};
static DEFINE_PER_CPU(struct rcu_dyntick, rcu_dyntick);
( fwiw, bool doesn't have a well specified storage type )
This way you have more control over the placement, variables are forced
to be together, instead of at the mercy of whatever per_cpu and the
linker do, and you more clearly see the holes in the structure.
All the per_cpu() usage should still work like:
per_cpu(rcu_dyntick.first_pass, cpu) = 0;
next prev parent reply other threads:[~2012-04-26 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 16:15 [PATCH RFC tip/core/rcu 0/4] Updates to RCU_FAST_NO_HZ Paul E. McKenney
2012-04-23 16:15 ` [PATCH RFC tip/core/rcu 1/4] rcu: Add RCU_FAST_NO_HZ tracing for idle exit Paul E. McKenney
2012-04-23 16:15 ` [PATCH RFC tip/core/rcu 2/4] rcu: Make RCU_FAST_NO_HZ use timer rather than hrtimer Paul E. McKenney
2012-04-23 16:16 ` [PATCH RFC tip/core/rcu 3/4] rcu: Make RCU_FAST_NO_HZ account for pauses out of idle Paul E. McKenney
2012-04-26 13:00 ` Peter Zijlstra [this message]
2012-04-26 14:49 ` Paul E. McKenney
2012-04-26 15:09 ` Peter Zijlstra
2012-04-23 16:16 ` [PATCH RFC tip/core/rcu 4/4] rcu: Ensure that RCU_FAST_NO_HZ timers expire on correct CPU Paul E. McKenney
2012-04-26 13:04 ` Peter Zijlstra
2012-04-26 15:54 ` Paul E. McKenney
2012-04-26 16:08 ` Steven Rostedt
2012-04-26 17:56 ` Paul E. McKenney
2012-04-26 18:10 ` [PATCH] timer: Fix mod_timer_pinned() header commen (was: [PATCH RFC tip/core/rcu 4/4] rcu: Ensure that RCU_FAST_NO_HZ timers expire on correct CPU) Steven Rostedt
2012-04-26 18:36 ` 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=1335445242.13683.19.camel@twins \
--to=peterz@infradead.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=paul.mckenney@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.