From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: <paulmck@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [RFC PATCH 0/2] tiny_rcu: simplify tiny_rcu
Date: Tue, 9 Dec 2014 17:43:11 +0800 [thread overview]
Message-ID: <5486C42F.7010407@cn.fujitsu.com> (raw)
In-Reply-To: <20141128154210.GX5050@linux.vnet.ibm.com>
On 11/28/2014 11:42 PM, Paul E. McKenney wrote:
> On Fri, Nov 28, 2014 at 05:43:31PM +0800, Lai Jiangshan wrote:
>> Hi, Paul
>>
>> These two patches use the special feture of the UP system:
>> In UP, quiescent state == grace period.
>>
>> For rcu_bh, rcu_process_callbacks() == a bh == QS == GP
>> so we can pass rcu_bh-QS and advance GP(and callbacks) in
>> rcu_process_callbacks(). After doing so, rcu_bh_qs() is useless
>> since its work is handled by rcu_process_callbacks().
>>
>> For rcu_sched, context-switch = QS = GP, thus we can force a
>> context-switch when call_rcu_sched() is happened on idle_task.
>> After doing so, rcu_idle/irq_enter/exit() are useless.
>>
>> These patches remove the useless code to simplify the tiny_rcu.
>>
>> We can change rcu_bh_qs() rcu_idle/irq_enter/exit() to static-inline-functions
>> to reduce the binary size after these two patches accepted.
>>
>> Thanks,
>> Lai
>
> These look interesting and promising!
>
> Could you please add the change in the tiny.o size to the commit logs?
>
> Also, one potential performance problem with this patchset is that it is
> moving the RAISE_SOFTIRQ() from the scheduling-clock interrupt handler
> (where it simply sets a bit in a per-CPU variable) to mainline code
> (where it is often a much more expensive full wakeup of ksoftirqd).
> My guess (and hope) is that this will be in the noise for most workloads,
> but given that there is some chance of performance regressions, could
> you please measure the performance difference on some reasonable
> benchmark? The kernbench benchmark should be just fine for this purpose.
Hi, Paul
The kernbench tests showed no performance changed. It is expected due
to kernbench doesn't hit any network code which use RCU_BH.
But I still drop the patch1 since I only benchmarked it by kernbench.
Thanks,
Lai
>
> Thanx, Paul
>
>> Cc: Josh Triplett <josh@joshtriplett.org>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
>> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>
>> Lai Jiangshan (2):
>> record rcu_bh quiescent state in RCU_SOFTIRQ
>> tiny_rcu: resched when call_rcu() on idle_task
>>
>> kernel/rcu/rcu.h | 6 ++
>> kernel/rcu/tiny.c | 134 ++++++++--------------------------------------
>> kernel/rcu/tiny_plugin.h | 2 +-
>> kernel/rcu/tree.c | 6 --
>> 4 files changed, 29 insertions(+), 119 deletions(-)
>>
>> --
>> 1.7.4.4
>>
>
> .
>
next prev parent reply other threads:[~2014-12-09 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 9:43 [RFC PATCH 0/2] tiny_rcu: simplify tiny_rcu Lai Jiangshan
2014-11-28 9:43 ` [RFC PATCH 1/2] record rcu_bh quiescent state in RCU_SOFTIRQ Lai Jiangshan
2014-11-28 9:43 ` [RFC PATCH 2/2] tiny_rcu: resched when call_rcu_sched() on idle_task Lai Jiangshan
2014-11-28 15:42 ` [RFC PATCH 0/2] tiny_rcu: simplify tiny_rcu Paul E. McKenney
2014-12-09 9:43 ` Lai Jiangshan [this message]
2014-12-09 9:53 ` [PATCH] tiny_rcu: directly force QS when call_rcu_[bh|sched]() on idle_task Lai Jiangshan
2014-12-09 17:02 ` 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=5486C42F.7010407@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).