From: "Paul E. McKenney" <paulmck@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
rcu@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Borkmann <daniel@iogearbox.net>,
Jiri Olsa <jolsa@redhat.com>, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [GIT PULL rcu-tasks-trace] 50x speedup for synchronize_rcu_tasks_trace()
Date: Wed, 23 Sep 2020 21:29:35 -0700 [thread overview]
Message-ID: <20200924042935.GV29330@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <CAADnVQJfmFjVRqJopeqy_7bHVdQ9x+i9d94Sv7Dshnh40FisTA@mail.gmail.com>
On Wed, Sep 23, 2020 at 07:46:15PM -0700, Alexei Starovoitov wrote:
> On Tue, Sep 22, 2020 at 9:25 AM Paul E. McKenney <paulmck@kernel.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.
Sounds very good, thank you! If problems arise, you know where
to find me. As do most of the people running these patches, I
would guess. ;-)
Thanx, Paul
prev parent reply other threads:[~2020-09-24 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:25 [GIT PULL rcu-tasks-trace] 50x speedup for synchronize_rcu_tasks_trace() Paul E. McKenney
2020-09-24 2:46 ` Alexei Starovoitov
2020-09-24 4:29 ` Paul E. McKenney [this message]
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=20200924042935.GV29330@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=tglx@linutronix.de \
/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