[bootlin/training-materials updates] master: Boot time: minor improvements (bcd4d7e3)

Michael Opdenacker michael.opdenacker at bootlin.com
Wed Oct 23 09:29:09 CEST 2019

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/bcd4d7e37c254955cd61558e0f07591c4b21fc73


commit bcd4d7e37c254955cd61558e0f07591c4b21fc73
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Oct 23 09:29:09 2019 +0200

    Boot time: minor improvements
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


 labs/boot-time-init-scripts/boot-time-init-scripts.tex     | 2 +-
 slides/boot-time-init-scripts3/boot-time-init-scripts3.tex | 2 +-
 slides/boot-time-toolchain2/boot-time-toolchain2.tex       | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/labs/boot-time-init-scripts/boot-time-init-scripts.tex b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
index c6a01363..04f92ffa 100644
--- a/labs/boot-time-init-scripts/boot-time-init-scripts.tex
+++ b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
@@ -281,7 +281,7 @@ shouldn't need any more. Do the same for \code{/root}, \code{/tmp},
 the \code{/lib32} link. We're keeping the \code{/proc} and \code{/sys}
 directories in case we need to mount the corresponding filesystems.
-Why doing this so aggressively for file we won't access? On an {\em
+Why doing this so aggressively for files we won't access? On an {\em
 ext4} filesystem, files that are not accessed may not do any harm if
 they are not used, except perhaps marginally in terms of mounting time
 (if the filesystem is unnecessarily big). However, if we store the root
diff --git a/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex b/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
index 032e49ac..0051aceb 100644
--- a/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
+++ b/slides/boot-time-init-scripts3/boot-time-init-scripts3.tex
@@ -10,7 +10,7 @@ application and then switch to the final root filesystem with
       You could even do without it and implement \code{/init} in C.
 \item Use statically linked applications (less CPU overhead, less
       libraries to load, smaller initramfs if no libraries at all).
-      \code{BR2_PREFER_STATIC_LIB} in Buildroot.
+      \code{BR2_STATIC_LIBS} in Buildroot.
diff --git a/slides/boot-time-toolchain2/boot-time-toolchain2.tex b/slides/boot-time-toolchain2/boot-time-toolchain2.tex
index d4dfd407..4e94ec4a 100644
--- a/slides/boot-time-toolchain2/boot-time-toolchain2.tex
+++ b/slides/boot-time-toolchain2/boot-time-toolchain2.tex
@@ -28,7 +28,7 @@ This gives you the best time that can possibly be achieved (with the fastest sto
 \item Compiled with gcc 7.4, generating {\em Thumb2} code:\\
       Total filesystem size: 3.10 MB (-18 \%)\\
       \code{ffmpeg} size: 183 KB (-19 \%)
-\item Performance aspect: performance apparently slightly improved
+\item Performance aspect: performance apparently slightly improved with Thumb2
       (approximately less than 5 \%, but there are slight variations in measured
       execution time, for one run to another).

More information about the training-materials-updates mailing list