linux-kernel - Re: [GIT PULL rcu-tasks-trace] 50x speedup for synchronize_rcu_tasks

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: <CAADnVQJfmFjVRqJopeqy_7bHVdQ9x+i9d94Sv7Dshnh40FisTA@mail.gmail.com>
Date:   Wed, 23 Sep 2020 19:46:15 -0700
From:   Alexei Starovoitov <alexei.starovoitov@...il.com>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     Alexei Starovoitov <ast@...nel.org>, rcu@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Daniel Borkmann <daniel@...earbox.net>,
        Jiri Olsa <jolsa@...hat.com>, bpf <bpf@...r.kernel.org>,
        Kernel Team <kernel-team@...com>
Subject: Re: [GIT PULL rcu-tasks-trace] 50x speedup for synchronize_rcu_tasks_trace()

On Tue, Sep 22, 2020 at 9:25 AM Paul E. McKenney <paulmck@...nel.org> wrote:
>
> Hello, Alexei,
>
> This pull request contains eight commits that speed up RCU Tasks Trace
> grace periods by a factor of 50, fix a few race conditions exposed
> by this speedup, and clean up a couple of minor issues.  These have
> been exposed to 0day and -next testing, and have passed well over 1,000
> hours of rcutorture testing, some of which has contained ad-hoc changes
> to further increase race probabilities.  So they should be solid!
> (Famous last words...)
>
> I would normally have sent this series up through -tip, but as we
> discussed, going up through the BFP and networking trees provides the
> needed exposure to real-world testing of these changes.  Please note
> that the first patch is already in mainline, but given identical SHA-1
> commit IDs, git should have no problem figuring this out.  I will also
> be retaining these commits in -rcu in order to continue exposing them
> to rcutorture testing, but again the identical SHA-1 commit IDs will
> make everything work out.

Pulled into bpf-next. Thanks a lot.

Also confirming 50x speedup.
Really nice to see that selftests/bpf are now fast again.

Not only all bpf developers will be running these patches now,
but the bpf CI system will be exercising them as well.