From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org, josh@joshtriplett.org,
zhong@linux.vnet.ibm.com, khilman@linaro.org,
geoff@infradead.org, tglx@linutronix.de,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH] nohz1: Documentation
Date: Thu, 21 Mar 2013 08:18:11 -0700 [thread overview]
Message-ID: <20130321151811.GR3637@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130321101650.GA11214@pd.tnic>
On Thu, Mar 21, 2013 at 11:16:50AM +0100, Borislav Petkov wrote:
> On Wed, Mar 20, 2013 at 07:22:59PM -0700, Paul E. McKenney wrote:
> > > > > > The "full_nohz=" boot parameter specifies which CPUs are to be
> > > > > > adaptive-ticks CPUs. For example, "full_nohz=1,6-8" says that CPUs 1,
> > > > >
> > > > > This is the first time you mention "adaptive-ticks". Probably should
> > > > > define it before just using it, even though one should be able to figure
> > > > > out what adaptive-ticks are, it does throw in a wrench when reading this
> > > > > if you have no idea what an "adaptive-tick" is.
> > > >
> > > > Good point, changed the first sentence of this paragraph to read:
> > > >
> > > > The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to
> > > > avoid sending scheduling-clock interrupts to CPUs with a single
> > > > runnable task, and such CPUs are said to be "adaptive-ticks CPUs".
> > >
> > > Sounds good.
>
> Yeah,
>
> so I read this last night too and I have to say, very clearly written,
> even for dummies like me.
Can't say that I think of you as a dummy, but glad you liked it!
> But this "adaptive-ticks CPUs" reads kinda strange throughout the whole
> text, it feels a bit weird. And since the cmdline option is called
> "full_nohz", you might just as well call them the "full_nohz CPUs" or
> the "full_nohz subset of CPUs" for simplicity and so that you don't have
> yet another new term in the text denoting the same idea. I mean, all
> those names kinda suck and need the full definition of what adaptive
> ticking actually means anyway. :)
I am happy with either "adaptive-ticks CPUs" or "full_nohz CPUs", and
leave the choice to Frederic.
> Btw, congrats on coining a new noun: "Adaptive-tick mode may prevent
> this round-robining from happening."
> ^^^^^^^^^^^^^^
Actually, this is a generic transformation. Given an English verb,
you almost always add "ing" to create a noun. Since "round-robin" is
used as a verb, as in "The scheduler will round-robin between the two
SCHED_RR tasks", "round-robining" may be used as a noun denoting the
action corresponding to the verb "round-robin". There is no doubt
an argument as to whether this should be spelled "round-robining" or
"round-robinning", but I will leave this to those who care enough to
argue about it. ;-)
> Funny. :-)
>
> I spose now one can say: "The kids in the garden are round-robining on
> the carousel."
>
> or
>
> "The kernel developers are round-robined for pull requests."
;-)
> Or maybe it wasn't you who coined it after /me doing a little search. It
> looks like technical people are pushing hard for it to be committed in
> the upstream English language repository. :-)
The thing about English is that it is an open-source language, and always
has been. English is defined by its usage, and the wise dictionary-makers
try their best to keep up. (The unwise ones attempt to stop the evolution
of the English language.) Everything good and everything bad about
English stems from this property. ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-03-21 15:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 16:29 [PATCH] nohz1: Documentation Paul E. McKenney
2013-03-18 18:13 ` Rob Landley
2013-03-18 18:46 ` Frederic Weisbecker
2013-03-18 19:59 ` Rob Landley
2013-03-18 20:48 ` Frederic Weisbecker
2013-03-18 22:25 ` Paul E. McKenney
2013-03-20 23:32 ` Steven Rostedt
2013-03-20 23:55 ` Paul E. McKenney
2013-03-21 0:27 ` Steven Rostedt
2013-03-21 2:22 ` Paul E. McKenney
2013-03-21 10:16 ` Borislav Petkov
2013-03-21 15:18 ` Paul E. McKenney [this message]
2013-03-21 16:00 ` Borislav Petkov
2013-03-21 15:45 ` Arjan van de Ven
2013-03-21 17:18 ` Paul E. McKenney
2013-03-21 17:41 ` Arjan van de Ven
2013-03-21 18:02 ` Paul E. McKenney
2013-03-22 18:37 ` Kevin Hilman
2013-03-22 19:25 ` Paul E. McKenney
2013-03-22 4:59 ` Rob Landley
2013-03-21 18:01 ` Frederic Weisbecker
2013-03-21 18:26 ` Paul E. McKenney
2013-03-21 16:08 ` Christoph Lameter
2013-03-21 17:15 ` Paul E. McKenney
2013-03-21 18:39 ` Christoph Lameter
2013-03-21 18:58 ` Paul E. McKenney
2013-03-21 20:04 ` Christoph Lameter
2013-03-21 20:42 ` Frederic Weisbecker
2013-03-21 21:02 ` Christoph Lameter
2013-03-21 21:06 ` Frederic Weisbecker
2013-03-21 20:50 ` Paul E. McKenney
2013-03-22 14:38 ` Christoph Lameter
2013-03-22 16:28 ` Paul E. McKenney
2013-03-25 14:31 ` Christoph Lameter
2013-03-25 14:37 ` Frederic Weisbecker
2013-03-25 15:18 ` Christoph Lameter
2013-03-25 15:20 ` Frederic Weisbecker
2013-03-22 9:52 ` Mats Liljegren
2013-03-22 19:01 ` Kevin Hilman
2013-03-21 18:44 ` Steven Rostedt
2013-03-21 18:53 ` Christoph Lameter
2013-03-21 19:16 ` Steven Rostedt
2013-03-21 18:59 ` Paul E. McKenney
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=20130321151811.GR3637@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=geoff@infradead.org \
--cc=josh@joshtriplett.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.com \
/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).