Re: [PATCH] nohz1: Documentation
From: Borislav Petkov
Date: Thu Mar 21 2013 - 06:17:00 EST
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.
so I read this last night too and I have to say, very clearly written,
even for dummies like me.
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. :)
Btw, congrats on coining a new noun: "Adaptive-tick mode may prevent
this round-robining from happening."
I spose now one can say: "The kids in the garden are round-robining on
"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. :-)
Sent from a fat crate under my desk. Formatting is fine.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/