From: Davidlohr Bueso <dave@stgolabs.net>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH-tip 3/3] locking/rwsem: Stop active read lock ASAP
Date: Sun, 26 Feb 2017 10:58:16 -0800 [thread overview]
Message-ID: <20170226185816.GF5126@linux-80c1.suse> (raw)
In-Reply-To: <1487786634-22641-4-git-send-email-longman@redhat.com>
On Wed, 22 Feb 2017, Waiman Long wrote:
>On a 2-socket 36-core 72-thread x86-64 E5-2699 v3 system, a rwsem
>microbenchmark was run with 36 locking threads (one/core) doing 100k
>reader and writer lock/unlock operations each, the resulting locking
>rates (avg of 3 runs) on a 4.10 kernel were 561.4 Mop/s and 588.8
>Mop/s without and with the patch respectively. That was an increase
>of about 5%.
iirc this patch is a repost, no? If so, did you get a chance to measure
single file access with direct io as dchinner suggested?
Thanks,
Davidlohr
next prev parent reply other threads:[~2017-02-26 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 18:03 [PATCH-tip 0/3] locking/rwsem: Minor twists to improve rwsem performance Waiman Long
2017-02-22 18:03 ` [PATCH-tip 1/3] locking/rwsem: Check wait_list without lock if spinner present Waiman Long
2017-02-26 18:49 ` Davidlohr Bueso
2017-02-27 15:02 ` Waiman Long
2017-02-22 18:03 ` [PATCH-tip 2/3] locking/rwsem: move down rwsem_down_read_failed() Waiman Long
2017-02-26 18:33 ` Davidlohr Bueso
2017-02-27 14:22 ` Waiman Long
2017-02-22 18:03 ` [PATCH-tip 3/3] locking/rwsem: Stop active read lock ASAP Waiman Long
2017-02-26 18:58 ` Davidlohr Bueso [this message]
2017-02-27 15:07 ` Waiman Long
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=20170226185816.GF5126@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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