From: Patrick Marlier <patrick.marlier@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: Steven Rostedt <rostedt@goodmis.org>, NeilBrown <neilb@suse.de>,
linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com,
wangyun@linux.vnet.ibm.com
Subject: Re: [PATCH tip/core/rcu 3/4] md/bitmap: Fix list_entry_rcu usage
Date: Wed, 23 Sep 2015 19:57:53 +0200 [thread overview]
Message-ID: <5602E821.800@gmail.com> (raw)
In-Reply-To: <20150922205000.GA29408@linux.vnet.ibm.com>
On 09/22/2015 10:50 PM, Paul E. McKenney wrote:
> On Sun, Sep 13, 2015 at 09:10:24AM -0700, Paul E. McKenney wrote:
>> On Sun, Sep 13, 2015 at 12:06:33PM +0200, Patrick Marlier wrote:
>
> [ . . . ]
>
>>> Paul,
>>>
>>> This sounds good to me. It should fix the performance issue (will
>>> check with my benchmark).
>>
>> Thank you, looking forward to seeing the results!
>
> Just following up -- how is the benchmarking going?
Note that in my module I am using the kernel version 3.16.0-31 (I ported
your change).
Here the results of my benchmark that tests rculist in the case of read
only.
# 1st column : The number of threads
# 2nd : ops/s the original version
# 3rd : ops/s your version with lockless_dereference
1 883923 1747554
2 1741441 3543062
3 2462360 5103647
4 3437273 7176608
6 5155803 9812348
8 6718111 13330050
10 8519227 17458294
12 9773632 20298897
14 11555198 23191424
16 11643264 25125712
I get same performance with my patch.
So indeed it fixes the performance problem I was seeing.
Thanks a lot!
--
Pat
next prev parent reply other threads:[~2015-09-23 17:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 22:46 [PATCH tip/core/rcu 0/4] RCU-protected list updates for 4.2 Paul E. McKenney
2015-05-12 22:46 ` [PATCH tip/core/rcu 1/4] rculist: Fix another sparse warning Paul E. McKenney
2015-05-12 22:46 ` [PATCH tip/core/rcu 2/4] rculist: Fix list_entry_rcu to read ptr with rcu_dereference_raw Paul E. McKenney
2015-05-12 22:46 ` [PATCH tip/core/rcu 3/4] md/bitmap: Fix list_entry_rcu usage Paul E. McKenney
2015-05-13 2:38 ` Steven Rostedt
2015-05-13 2:58 ` NeilBrown
2015-05-13 13:17 ` Paul E. McKenney
2015-05-16 17:42 ` Patrick Marlier
2015-05-18 2:06 ` NeilBrown
2015-05-18 13:43 ` Steven Rostedt
2015-05-19 22:07 ` Paul E. McKenney
2015-05-20 5:09 ` NeilBrown
2015-05-20 13:28 ` Paul E. McKenney
2015-05-21 0:07 ` NeilBrown
2015-09-11 23:05 ` Paul E. McKenney
2015-09-13 10:06 ` Patrick Marlier
2015-09-13 16:10 ` Paul E. McKenney
2015-09-22 20:50 ` Paul E. McKenney
2015-09-23 17:57 ` Patrick Marlier [this message]
2015-09-24 4:45 ` Paul E. McKenney
2015-05-18 13:53 ` Patrick Marlier
2015-05-18 19:36 ` Patrick Marlier
2015-05-12 22:46 ` [PATCH tip/core/rcu 4/4] netfilter: " Paul E. McKenney
2015-05-13 2:42 ` Steven Rostedt
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=5602E821.800@gmail.com \
--to=patrick.marlier@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wangyun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox