On Mon, Nov 07, 2016 at 02:52:33AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
Queued, thank you!
Thanx, Paul
> ---
> rt/rt.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rt/rt.tex b/rt/rt.tex
> index 21a53a4514b8..870bc9af6e0b 100644
> --- a/rt/rt.tex
> +++ b/rt/rt.tex
> @@ -386,7 +386,7 @@ cylinder contained in the log to the blade,
> Each of these six phases of operation might well have its own set of
> deadlines and environmental constraints,
> for example, one would expect phase~4's deadlines to be much more severe
> -than those of phase 6, milliseconds instead of seconds.
> +than those of phase~6, milliseconds instead of seconds.
> One might therefore expect that low-priority work would be performed in
> phase~6 rather than in phase~4.
> That said, careful choices of hardware, drivers, and software configuration
> @@ -1429,7 +1429,7 @@ only being one runnable task on that CPU is said to be in
> \emph{adaptive ticks mode}.
>
> As an alternative to the \co{nohz_full=} boot parameter, you can build
> -your kernel with \co{NO_HZ_FULL_ALL}, which will designate CPU 0 as
> +your kernel with \co{NO_HZ_FULL_ALL}, which will designate CPU~0 as
> a housekeeping CPU and all other CPUs as worker CPUs.
> Either way, it is important to ensure that you have designated enough
> housekeeping CPUs to handle the housekeeping load imposed by the
> --
> 2.10.0
>
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
