From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Andrew Morton <akpm@osdl.org>,
Dipankar Sarma <dipankar@in.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [patch] RCU: introduce rcu_soon_pending() interface
Date: Mon, 24 Apr 2006 13:11:41 +0200 [thread overview]
Message-ID: <20060424111141.GC16007@osiris.boeblingen.de.ibm.com> (raw)
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Introduce rcu_soon_pending() interface. This can be used to tell if there
will be a new rcu batch on a cpu soon by looking at the curlist pointer.
This can be used to avoid to enter a tickless idle state where the cpu
would miss that a new batch is ready when rcu_start_batch would be called
on a different cpu.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---
See also here: http://www.ussg.iu.edu/hypermail/linux/kernel/0604.3/0057.html
Better solutions welcome :)
include/linux/rcupdate.h | 1 +
kernel/rcupdate.c | 8 ++++++++
2 files changed, 9 insertions(+)
diff --git a/include/linux/rcupdate.h b/include/linux/rcupdate.h
index 5673008..80bcbce 100644
--- a/include/linux/rcupdate.h
+++ b/include/linux/rcupdate.h
@@ -132,6 +132,7 @@ static inline void rcu_bh_qsctr_inc(int
}
extern int rcu_pending(int cpu);
+extern int rcu_soon_pending(int cpu);
/**
* rcu_read_lock - mark the beginning of an RCU read-side critical section.
diff --git a/kernel/rcupdate.c b/kernel/rcupdate.c
index 13458bb..e8cf09f 100644
--- a/kernel/rcupdate.c
+++ b/kernel/rcupdate.c
@@ -485,6 +485,14 @@ int rcu_pending(int cpu)
__rcu_pending(&rcu_bh_ctrlblk, &per_cpu(rcu_bh_data, cpu));
}
+int rcu_soon_pending(int cpu)
+{
+ struct rcu_data *rdp = &per_cpu(rcu_data, cpu);
+ struct rcu_data *rdp_bh = &per_cpu(rcu_bh_data, cpu);
+
+ return (!!rdp->curlist || !!rdp_bh->curlist);
+}
+
void rcu_check_callbacks(int cpu, int user)
{
if (user ||
next reply other threads:[~2006-04-24 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 11:11 Heiko Carstens [this message]
2006-04-24 23:09 ` [patch] RCU: introduce rcu_soon_pending() interface Andrew Morton
2006-04-25 5:27 ` Heiko Carstens
2006-04-25 11:46 ` Paul E. McKenney
2006-04-25 11:52 ` Heiko Carstens
2006-04-25 12:08 ` Paul E. McKenney
2006-04-25 12:27 ` [patch] RCU: introduce rcu_needs_cpu() interface Heiko Carstens
[not found] ` <20060426141205.58675763.akpm@osdl.org>
2006-04-27 8:11 ` [patch] RCU: add comments to rcu_pending/rcu_needs_cpu Heiko Carstens
2006-05-01 21:57 ` Paul E. McKenney
2006-05-02 6:35 ` Heiko Carstens
2006-04-25 12:28 ` [patch] s390: exploit rcu_needs_cpu() interface Heiko Carstens
2006-04-25 11:23 ` [patch] RCU: introduce rcu_soon_pending() interface Paul E. McKenney
2006-04-25 11:33 ` Martin Schwidefsky
2006-04-25 11:48 ` 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=20060424111141.GC16007@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=schwidefsky@de.ibm.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