linux-kernel - Re: [PATCH v5 00/18] locking/rwsem: Rwsem rearchitecture part 2

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <8f1adff7-3bd4-7d35-1a0d-698662bfa2b8@redhat.com>
Date:   Thu, 18 Apr 2019 19:56:03 -0400
From:   Waiman Long <longman@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Will Deacon <will.deacon@....com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>
Cc:     linux-kernel@...r.kernel.org, x86@...nel.org,
        Davidlohr Bueso <dave@...olabs.net>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Tim Chen <tim.c.chen@...ux.intel.com>,
        huang ying <huang.ying.caritas@...il.com>
Subject: Re: [PATCH v5 00/18] locking/rwsem: Rwsem rearchitecture part 2

On 04/18/2019 07:46 PM, Waiman Long wrote:
>  v5:
>   - Drop v4 patch 1 as it is merged into tip's locking/core branch.
>   - Integrate the 2 followup patches into the series. The first
>     follow-up patch is broken into 2 pieces. The first piece comes in
>     before the "Enable readers spinning on writer" and the 2nd piece
>     is merged into the "Enable time-based spinning on reader-owned
>     rwsem" patch. The 2nd followup patch is added after that.
>   - Add a new patch to make all wake_up_q() calls after dropping
>     wait_lock as suggested by PeterZ.
>   - Incorporate numerouos suggestions by PeterZ and Davidlohr.

This patchset is still being reviewed by Peter . The purpose of this
series is mainly to sync up the version that Peter has and the ones that
I am working on incorporating his feedback. Further changes may still be
needed.

I run an overall performance test on this new patchset and present the
data in this cover letter. However, I haven't run performance tests for
individual patches. So the performance data listed in some of the
patches may be stale.

Cheers,
Longman