From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: paulmck@linux.vnet.ibm.com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
David Miller <davem@davemloft.net>,
Manfred Spraul <manfred@colorfullife.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
dipankar@in.ibm.com
Subject: Re: [PATCH, RFC] RCU: New scalable, multi-GP and preemptible RCU implementation
Date: Wed, 15 Sep 2010 17:43:12 +0800 [thread overview]
Message-ID: <4C909530.1070808@cn.fujitsu.com> (raw)
In-Reply-To: <20100913231756.GB18902@linux.vnet.ibm.com>
On 09/14/2010 07:17 AM, Paul E. McKenney wrote:
>>>>
>>>> Only in x86(32bit and 64bit) system.
>>>> Did you patch it in power and test it? It' need more test for different archs,
>>>> but I have no other arch.
>>>>
>>>> What is "hardware configuration"?
>>>
>>> Mainly the number of CPUs. The socket/core/thread counts could also
>>> be helpful.
>
> Any info? ;-)
>
Ouch, answer this first:
hardware1: x86, 1cpu X 2cores
hardware2: x86_64, 2cpu X 2cores
48 hours rcutorture for each machine, (NO_HZ, cpu_plugin concurrently ... )
~120 minutes rcutorture for each different CONFIG.
this work is my own work, not my company's, I can't access to
big machines.
Lai.
next prev parent reply other threads:[~2010-09-15 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:31 [PATCH, RFC] RCU: New scalable, multi-GP and preemptible RCU implementation Lai Jiangshan
2010-08-30 23:57 ` Paul E. McKenney
2010-08-31 3:03 ` Lai Jiangshan
2010-09-08 19:53 ` Paul E. McKenney
2010-09-13 12:27 ` Lai Jiangshan
2010-09-13 23:17 ` Paul E. McKenney
2010-09-15 9:43 ` Lai Jiangshan [this message]
2010-09-16 6: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=4C909530.1070808@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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