From: "Paul E. McKenney" <paulmck@kernel.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
x86 <x86@kernel.org>
Subject: Re: [PATCH] rcu/performance: Fix kfree_perf_init() build warning on 32-bit kernels
Date: Wed, 17 Jun 2020 11:06:06 -0700 [thread overview]
Message-ID: <20200617180606.GA23728@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200603181109.GA5438@paulmck-ThinkPad-P72>
On Wed, Jun 03, 2020 at 11:11:09AM -0700, Paul E. McKenney wrote:
> On Tue, May 26, 2020 at 09:14:13PM -0400, Joel Fernandes wrote:
> > On Tue, May 26, 2020 at 08:27:44PM +0200, Ingo Molnar wrote:
[ . . . ]
> > > BTW., could we please also rename this code from 'PERF_TEST'/'perf test'
> > > to 'PERFORMANCE_TEST'/'performance test'? At first glance I always
> > > mistakenly believe that it's somehow related to perf, while it isn't. =B-)
> >
> > Would it be better to call it 'RCUPERF_TEST' instead of the
> > 'RCU_PERFORMANCE_TEST' you are proposing? I feel the word 'PERFORMANCE' is
> > too long. Also, 'rcuperf test' instead of the 'rcu performance test' you are
> > proposing. I am Ok with doing it however you and Paul want it though, let me
> > know.
>
> As long as we are bikeshedding the name... How about refscale.c and
> RCU_REF_SCALE_TEST on the one hand and rcuscale.c and RCU_SCALE_TEST on
> the other? That keeps the names reasonably short and does not allude
> to perf at all.
Hearing no objections, I will go with the scale/SCALE names.
Thanx, Paul
prev parent reply other threads:[~2020-06-17 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 20:59 [tip: core/rcu] rcuperf: Add ability to increase object allocation size tip-bot2 for Joel Fernandes (Google)
2020-05-26 18:27 ` [PATCH] rcu/performance: Fix kfree_perf_init() build warning on 32-bit kernels Ingo Molnar
2020-05-26 19:14 ` Paul E. McKenney
2020-06-02 9:57 ` Geert Uytterhoeven
2020-06-02 15:56 ` Paul E. McKenney
2020-05-27 1:14 ` Joel Fernandes
2020-06-03 18:11 ` Paul E. McKenney
2020-06-17 18:06 ` 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=20200617180606.GA23728@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).