From: Steven Rostedt <rostedt@goodmis.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Paul McKenney <paulmck@kernel.org>,
Anton Blanchard <anton@ozlabs.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: speed up buffer resets by avoiding synchronize_rcu for each CPU
Date: Mon, 29 Jun 2020 18:16:25 -0400 [thread overview]
Message-ID: <20200629181625.4b87a63a@oasis.local.home> (raw)
In-Reply-To: <20200625053403.2386972-1-npiggin@gmail.com>
On Thu, 25 Jun 2020 15:34:03 +1000
Nicholas Piggin <npiggin@gmail.com> wrote:
> Batch these up so we disable all the per-cpu buffers first, then
> synchronize_rcu() once, then reset each of the buffers. This brings
> the time down to about 0.5s.
After applying this patch, running tools/testing/selftests/ftracetest
went from 5 minutes and 35 seconds to 5 minutes 5 seconds to complete
on my 4 core (8 with hyperthreading) machine! That's almost a 10% drop!
Thanks, I'm definitely applying this for the next merge window.
-- Steve
next prev parent reply other threads:[~2020-06-29 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 5:34 Nicholas Piggin
2020-06-25 21:42 ` Anton Blanchard
2020-06-29 15:35 ` Paul E. McKenney
2020-06-29 15:40 ` Steven Rostedt
2020-06-29 22:16 ` Steven Rostedt [this message]
2020-06-30 2:07 ` Nicholas Piggin
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=20200629181625.4b87a63a@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=anton@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=paulmck@kernel.org \
/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
all inboxes | Powered by JetHome®