Skip to contentSkip to conversation

rt: Insert missing NBSPs

PATCH Applied SeongJae Park 2 participants 3 messages Nov 6, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/2 rt: Insert missing NBSPs

---
 rt/rt.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
rt/rt.tex +2 -2
index 21a53a4514b8..870bc9af6e0b 100644
@@ -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
Signature · 1 line
2.10.0
#1 lore raw

PATCH 2/2 rt: Fix a typo: soo -> so

---
 rt/rt.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
rt/rt.tex +1 -1
index 870bc9af6e0b..6fbc8dde0808 100644
@@ -1849,7 +1849,7 @@ on lines~17-35.
 	the call to \co{malloc()}???
 \QuickQuizAnswer{
 	In early 2016, situations forbidding runtime memory were
-	also not soo excited with multithreaded computing.
+	also not so excited with multithreaded computing.
 	So the runtime memory allocation is not an additional
 	obstacle to safety criticality.
 } \QuickQuizEnd
Signature · 1 line
2.10.0
#2 lore raw
In reply to SeongJae Park
Quoted 1 line · SeongJae Park

Queued, thank you!

Thanx, Paul

Quoted 29 lines
---
 rt/rt.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
rt/rt.tex +2 -2
index 21a53a4514b8..870bc9af6e0b 100644
@@ -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
Signature · 1 line
2.10.0