From: Ingo Molnar <mingo@elte.hu>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
Gautham Shenoy <ego@in.ibm.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH 2/2] rcu classic: new algorithm for callbacks-processing(v2)
Date: Fri, 18 Jul 2008 16:09:30 +0200 [thread overview]
Message-ID: <20080718140930.GT6875@elte.hu> (raw)
In-Reply-To: <48708F2F.2060406@cn.fujitsu.com>
* Lai Jiangshan <laijs@cn.fujitsu.com> wrote:
> This is v2, it's a little deference from v1 that I
> had send to lkml.
> use ACCESS_ONCE
> use rcu_batch_after/rcu_batch_before for batch # comparison.
>
> rcutorture test result:
> (hotplugs: do cpu-online/offline once per second)
>
> No CONFIG_NO_HZ: OK, 12hours
> No CONFIG_NO_HZ, hotplugs: OK, 12hours
> CONFIG_NO_HZ=y: OK, 24hours
> CONFIG_NO_HZ=y, hotplugs: Failed.
> (Failed also without my patch applied, exactly the same bug occurred,
> http://lkml.org/lkml/2008/7/3/24)
thanks, i've applied this to tip/core/rcu - but it would be nice have an
ack/nak from Paul as well, before we can proceed further.
Ingo
next prev parent reply other threads:[~2008-07-18 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 9:23 [RFC][PATCH 2/2] rcu classic: new algorithm for callbacks-processing(v2) Lai Jiangshan
2008-07-18 14:09 ` Ingo Molnar [this message]
2008-08-01 21:10 ` Paul E. McKenney
[not found] ` <20080721100433.GC8384@linux.vnet.ibm.com>
2008-08-01 21:10 ` Paul E. McKenney
2008-08-03 8:01 ` Lai Jiangshan
2008-08-04 22:54 ` Paul E. McKenney
2008-08-06 7:08 ` Lai Jiangshan
2008-08-07 3:19 ` Paul E. McKenney
[not found] ` <20080725165454.GA7147@linux.vnet.ibm.com>
2008-08-01 21:11 ` 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=20080718140930.GT6875@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.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 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.