lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 26 Feb 2017 10:58:16 -0800
From:   Davidlohr Bueso <>
To:     Waiman Long <>
Cc:     Ingo Molnar <>,
        Peter Zijlstra <>,
Subject: Re: [PATCH-tip 3/3] locking/rwsem: Stop active read lock ASAP

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?


Powered by blists - more mailing lists