From: Waiman Long <waiman.long@hp.com>
To: Jason Low <jason.low2@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH v2] locking/rwsem: reduce spinlock contention in wakeup after up_read/up_write
Date: Fri, 24 Apr 2015 10:55:30 -0400 [thread overview]
Message-ID: <553A5962.3040602@hp.com> (raw)
In-Reply-To: <1429821758.20330.6.camel@j-VirtualBox>
On 04/23/2015 04:42 PM, Jason Low wrote:
> On Thu, 2015-04-23 at 14:24 -0400, Waiman Long wrote:
>
>> The table below shows the % improvement in throughput (1100-2000 users)
>> in the various AIM7's workloads:
>>
>> Workload % increase in throughput
> Missing table here? :)
>
>
Oops, it was a cut-and-paste error. Will send out a new one to fix that.
Cheers,
Longman
next prev parent reply other threads:[~2015-04-24 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 18:24 [PATCH v2] locking/rwsem: reduce spinlock contention in wakeup after up_read/up_write Waiman Long
2015-04-23 20:42 ` Jason Low
2015-04-24 14:55 ` Waiman Long [this message]
2015-04-23 21:31 ` Davidlohr Bueso
2015-04-24 14:56 ` 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=553A5962.3040602@hp.com \
--to=waiman.long@hp.com \
--cc=doug.hatch@hp.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.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