From: Joe Korty <joe.korty@ccur.com>
To: paulmck@linux.vnet.ibm.com
Cc: fweisbec@gmail.com, peterz@infradead.org, laijs@cn.fujitsu.com,
mathieu.desnoyers@efficios.com, dhowells@redhat.com,
loic.minier@linaro.org, dhaval.giani@gmail.com,
tglx@linutronix.de, josh@joshtriplett.org,
houston.jim@comcast.net, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 13/24] jrcu: tuneable watchdog
Date: Thu, 24 Mar 2011 13:48:02 -0400 [thread overview]
Message-ID: <20110324174802.GA18893@tsunami.ccur.com> (raw)
jrcu: Make the watchdog value a tuneable.
Also increase the default to 30 seconds.
Signed-off-by: Joe Korty <joe.korty@ccur.com>
Index: b/kernel/jrcu.c
===================================================================
--- a/kernel/jrcu.c
+++ b/kernel/jrcu.c
@@ -139,6 +139,8 @@ int rcu_scheduler_active __read_mostly;
int rcu_nmi_seen __read_mostly;
static u64 rcu_timestamp;
+int rcu_wdog = 30; /* rcu watchdog interval, in seconds */
+
/*
* Return our CPU id or zero if we are too early in the boot process to
* know what that is. For RCU to work correctly, a cpu named '0' must
@@ -327,7 +329,7 @@ static void __rcu_delimit_batches(struct
*/
rcu_now = sched_clock();
if (!eob && !rcu_timestamp
- && ((rcu_now - rcu_timestamp) > 3LL * NSEC_PER_SEC)) {
+ && ((rcu_now - rcu_timestamp) > (s64)rcu_wdog * NSEC_PER_SEC)) {
rcu_stats.nforced++;
WARN_ON_ONCE(1);
eob = 1;
@@ -576,6 +578,7 @@ static int rcu_debugfs_show(struct seq_f
raw_local_irq_enable();
seq_printf(m, "%14u: hz\n", rcu_hz);
+ seq_printf(m, "%14u: watchdog (secs)\n", rcu_wdog);
#ifdef CONFIG_JRCU_DAEMON
if (rcu_daemon)
seq_printf(m, "%14u: daemon priority\n", rcu_priority);
@@ -671,6 +674,12 @@ static ssize_t rcu_debugfs_write(struct
return -EINVAL;
rcu_hz = rcu_hz_wanted;
rcu_hz_period_us = USEC_PER_SEC / rcu_hz;
+ } else if (!strncmp(token, "wdog=", 5)) {
+ int wdog = -1;
+ sscanf(&token[5], "%d", &wdog);
+ if (wdog < 3 || wdog > 1000)
+ return -EINVAL;
+ rcu_wdog = wdog;
} else
return -EINVAL;
reply other threads:[~2011-03-24 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110324174802.GA18893@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=andi@firstfloor.org \
--cc=dhaval.giani@gmail.com \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=houston.jim@comcast.net \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.minier@linaro.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome