From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/2] rt: Insert missing NBSPs
Date: Sun, 6 Nov 2016 15:28:49 -0800 [thread overview]
Message-ID: <20161106232849.GK24166@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161106175234.13878-1-sj38.park@gmail.com>
On Mon, Nov 07, 2016 at 02:52:33AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
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
>
prev parent reply other threads:[~2016-11-06 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 17:52 [PATCH 1/2] rt: Insert missing NBSPs SeongJae Park
2016-11-06 17:52 ` [PATCH 2/2] rt: Fix a typo: soo -> so SeongJae Park
2016-11-06 23:28 ` 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=20161106232849.GK24166@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.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