[FE training-materials-updates] Replace "user-space" by "user space"
Michael Opdenacker
michael.opdenacker at free-electrons.com
Fri May 23 18:49:45 CEST 2014
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=5b39472af776f0643841c3732248f69fea6fe8f1
>---------------------------------------------------------------
commit 5b39472af776f0643841c3732248f69fea6fe8f1
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Fri May 23 18:48:23 2014 +0200
Replace "user-space" by "user space"
- Following Wikepedia's convention
- Suggested by Robert P.J. Day (thanks!)
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
5b39472af776f0643841c3732248f69fea6fe8f1
agenda/boottime-agenda.tex | 2 +-
labs/boottime-measuring/boottime-measuring.tex | 4 ++--
.../android-build-system-advanced-product.tex | 2 +-
.../android-kernel-changes-ion.tex | 2 +-
.../boottime-init-scripts3.tex | 2 +-
.../kernel-driver-development-debugging.tex | 2 +-
.../kernel-driver-development-io-memory.tex | 2 +-
.../kernel-driver-development-memory.tex | 10 ++++----
.../syscalls.dia | 2 +-
.../kernel-driver-development-sleeping.tex | 2 +-
slides/kernel-frameworks/kernel-frameworks.tex | 24 ++++++++++----------
.../kernel-misc-subsystem.tex | 4 ++--
.../kernel-source-code-drivers.tex | 6 ++---
slides/sysdev-block-filesystems/journal.dia | 2 +-
.../sysdev-linux-intro-features.tex | 2 +-
slides/sysdev-realtime/sysdev-realtime.tex | 22 +++++++++---------
slides/sysdev-udev/sysdev-udev.tex | 2 +-
17 files changed, 46 insertions(+), 46 deletions(-)
diff --git a/agenda/boottime-agenda.tex b/agenda/boottime-agenda.tex
index 92a16e8..5e2fc17 100644
--- a/agenda/boottime-agenda.tex
+++ b/agenda/boottime-agenda.tex
@@ -135,7 +135,7 @@ Boot Time Optimization Training\\
\begin{itemize}
\item Regenerate the root filesystem with Buildroot
\item Use bootchart to measure boot time
- \item Simplify user-space scripts
+ \item Simplify user space scripts
\end{itemize}
}
diff --git a/labs/boottime-measuring/boottime-measuring.tex b/labs/boottime-measuring/boottime-measuring.tex
index 905ea77..93a1698 100644
--- a/labs/boottime-measuring/boottime-measuring.tex
+++ b/labs/boottime-measuring/boottime-measuring.tex
@@ -193,9 +193,9 @@ You can see that the above command automatically picks up the right
pre-compiled environment, depending on whether you have a 32 bit or
a 64 bit version of Ubuntu.
-\section{Study how user-space boots}
+\section{Study how user space boots}
-It's important to understand how the various user-space programs
+It's important to understand how the various user space programs
are started in the system. They all originate from the \code{init}
program, which is the first and only program executed by the Linux
kernel \footnote{There is one exception: the kernel can also run
diff --git a/slides/android-build-system-advanced-product/android-build-system-advanced-product.tex b/slides/android-build-system-advanced-product/android-build-system-advanced-product.tex
index e684024..9c0d4cc 100644
--- a/slides/android-build-system-advanced-product/android-build-system-advanced-product.tex
+++ b/slides/android-build-system-advanced-product/android-build-system-advanced-product.tex
@@ -178,7 +178,7 @@ USE_CAMERA_STUB := true
\begin{frame}[fragile]
\frametitle{Kernel Integration into Android}
\begin{itemize}
- \item Android is just a user-space software stack, the build system
+ \item Android is just a user space software stack, the build system
isn't designed to build the kernel
\item However, there is some facilities to integrate a precompiled
kernel kernel into the Android images
diff --git a/slides/android-kernel-changes-ion/android-kernel-changes-ion.tex b/slides/android-kernel-changes-ion/android-kernel-changes-ion.tex
index 6ebb116..e591f4d 100644
--- a/slides/android-kernel-changes-ion/android-kernel-changes-ion.tex
+++ b/slides/android-kernel-changes-ion/android-kernel-changes-ion.tex
@@ -34,7 +34,7 @@
\item[carveout] Large physically contiguous memory, preallocated
at boot
\end{description}
- \item It also has a user-space interface so that processes can
+ \item It also has a user space interface so that processes can
allocate memory to work on.
\item \url{https://lwn.net/Articles/480055/}
\end{itemize}
diff --git a/slides/boottime-init-scripts3/boottime-init-scripts3.tex b/slides/boottime-init-scripts3/boottime-init-scripts3.tex
index 4215b3f..c7ed7d1 100644
--- a/slides/boottime-init-scripts3/boottime-init-scripts3.tex
+++ b/slides/boottime-init-scripts3/boottime-init-scripts3.tex
@@ -154,6 +154,6 @@ and even create an animation!
{Reducing time in init-scripts}
{
\begin{itemize}
-\item Simplify user-space scripts
+\item Simplify user space scripts
\end{itemize}
}
diff --git a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
index 3c5cc36..8012bdd 100644
--- a/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
+++ b/slides/kernel-driver-development-debugging/kernel-driver-development-debugging.tex
@@ -81,7 +81,7 @@
\frametitle{DebugFS}
\begin{itemize}
\item A virtual filesystem to export debugging information to
- user-space.
+ user space.
\begin{itemize}
\item Kernel configuration: \code{DEBUG_FS}
\begin{itemize}
diff --git a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
index 03f0bdf..f1d938a 100644
--- a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
+++ b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
@@ -267,7 +267,7 @@ __raw_writel(1 << KS8695_IRQ_UART_TX,
\begin{frame}
\frametitle{/dev/mem}
\begin{itemize}
- \item Used to provide user-space applications with direct access to
+ \item Used to provide user space applications with direct access to
physical addresses.
\item Usage: open \code{/dev/mem} and read or write at given offset.
What you read or write is the value at the corresponding physical
diff --git a/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex b/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
index f67ecf0..3a921b6 100644
--- a/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
+++ b/slides/kernel-driver-development-memory/kernel-driver-development-memory.tex
@@ -21,7 +21,7 @@
\item Most memory can be a direct mapping of physical memory at
a fixed offset
\end{itemize}
- \item Complete 3GB exclusive mapping available for each user-space
+ \item Complete 3GB exclusive mapping available for each user space
process
\begin{itemize}
\item Process code and data (program, stack, ...)
@@ -48,7 +48,7 @@
virtual address space
\item If more physical memory is present on the platform, part of
the memory will not be accessible by kernel space, but can be used
- by user-space
+ by user space
\item To allow the kernel to access more physical memory:
\begin{itemize}
\item Change 1GB/3GB memory split (2GB/2GB)
@@ -79,15 +79,15 @@
architecture
\item Adds some address extension bits used to index memory areas
\item Allows accessing up to 64 GB of physical memory on x86
- \item Note that each user-space process is still limited to a 3 GB
+ \item Note that each user space process is still limited to a 3 GB
memory space
\end{itemize}
\end{frame}
\begin{frame}
- \frametitle{Notes on user-space memory}
+ \frametitle{Notes on user space memory}
\begin{itemize}
- \item New user-space memory is allocated either from the already
+ \item New user space memory is allocated either from the already
allocated process memory, or using the \code{mmap} system call
\item Note that memory allocated may not be physically allocated:
\begin{itemize}
diff --git a/slides/kernel-driver-development-processes/syscalls.dia b/slides/kernel-driver-development-processes/syscalls.dia
index ead61e7..8ff6fbf 100644
--- a/slides/kernel-driver-development-processes/syscalls.dia
+++ b/slides/kernel-driver-development-processes/syscalls.dia
@@ -319,7 +319,7 @@
<dia:composite type="text">
<dia:attribute name="string">
<dia:string>#Kernel code executed
-on behalf of user-space
+on behalf of user space
(can be preempted too!)#</dia:string>
</dia:attribute>
<dia:attribute name="font">
diff --git a/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex b/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
index 9d90490..37d2382 100644
--- a/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
+++ b/slides/kernel-driver-development-sleeping/kernel-driver-development-sleeping.tex
@@ -42,7 +42,7 @@ init_waitqueue_head(&queue);
\begin{itemize}
\item Sleeps until the task is woken up and the given C
expression is true. Caution: can't be interrupted (can't kill
- the user-space process!)
+ the user space process!)
\end{itemize}
\item \mint{c}+int wait_event_killable(queue, condition);+
\begin{itemize}
diff --git a/slides/kernel-frameworks/kernel-frameworks.tex b/slides/kernel-frameworks/kernel-frameworks.tex
index a5cd324..bca9c85 100644
--- a/slides/kernel-frameworks/kernel-frameworks.tex
+++ b/slides/kernel-frameworks/kernel-frameworks.tex
@@ -174,7 +174,7 @@ struct file_operations {
\begin{itemize}
\item \mint{c}+int foo_open(struct inode *i, struct file *f)+
\begin{itemize}
- \item Called when user-space opens the device file.
+ \item Called when user space opens the device file.
\item \kstruct{inode} is a structure that uniquely represents a file
in the system (be it a regular file, a directory, a symbolic
link, a character or block device)
@@ -192,7 +192,7 @@ struct file_operations {
\end{itemize}
\item \mint{c}+int foo_release(struct inode *i, struct file *f)+
\begin{itemize}
- \item Called when user-space closes the file.
+ \item Called when user space closes the file.
\end{itemize}
\end{itemize}
\end{frame}
@@ -203,10 +203,10 @@ struct file_operations {
\item \mint{c}+ssize_t foo_read(struct file *f, __user char *buf,+
\mint{c}+size_t sz, loff_t *off)+
\begin{itemize}
- \item Called when user-space uses the \code{read()} system call on
+ \item Called when user space uses the \code{read()} system call on
the device.
\item Must read data from the device, write at most \code{sz}
- bytes in the user-space buffer \code{buf}, and update the
+ bytes in the user space buffer \code{buf}, and update the
current position in the file \code{off}. \code{f} is a pointer
to the same file structure that was passed in the \code{open()}
operation
@@ -223,7 +223,7 @@ struct file_operations {
\item \mint{c}+ssize_t foo_write(struct file *f,+
\mint{c}+__user const char *buf, size_t sz, loff_t *off)+
\begin{itemize}
- \item Called when user-space uses the \code{write()} system call
+ \item Called when user space uses the \code{write()} system call
on the device
\item The opposite of \code{read}, must read at most \code{sz}
bytes from \code{buf}, write it to the device, update \code{off}
@@ -233,9 +233,9 @@ struct file_operations {
\end{frame}
\begin{frame}
- \frametitle{Exchanging data with user-space 1/3}
+ \frametitle{Exchanging data with user space 1/3}
\begin{itemize}
- \item Kernel code isn't allowed to directly access user-space
+ \item Kernel code isn't allowed to directly access user space
memory, using \kfunc{memcpy} or direct pointer dereferencing
\begin{itemize}
\item Doing so does not work on some architectures
@@ -244,23 +244,23 @@ struct file_operations {
\end{itemize}
\item To keep the kernel code portable and have proper error
handling, your driver must use special kernel functions to
- exchange data with user-space.
+ exchange data with user space.
\end{itemize}
\end{frame}
\begin{frame}[fragile]
- \frametitle{Exchanging data with user-space 2/3}
+ \frametitle{Exchanging data with user space 2/3}
\begin{itemize}
\item A single value
\begin{itemize}
\item \code{get_user(v, p);}
\begin{itemize}
\item The kernel variable \code{v} gets the value pointed by the
- user-space pointer \code{p}
+ user space pointer \code{p}
\end{itemize}
\item \code{put_user(v, p);}
\begin{itemize}
- \item The value pointed by the user-space pointer \code{p} is
+ \item The value pointed by the user space pointer \code{p} is
set to the contents of the kernel variable \code{v}.
\end{itemize}
\end{itemize}
@@ -277,7 +277,7 @@ struct file_operations {
\end{frame}
\begin{frame}
- \frametitle{Exchanging data with user-space 3/3}
+ \frametitle{Exchanging data with user space 3/3}
\begin{center}
\includegraphics[width=\textwidth]{slides/kernel-frameworks/copy-to-from-user.pdf}
\end{center}
diff --git a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
index abcc1ad..465ea45 100644
--- a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
+++ b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
@@ -75,10 +75,10 @@ struct miscdevice {
\end{itemize}
\end{frame}
-\begin{frame}{User-space API for misc devices}
+\begin{frame}{User space API for misc devices}
\begin{itemize}
\item {\em misc devices} are regular character devices
- \item The operations they support in user-space depends on the
+ \item The operations they support in user space depends on the
operations the kernel driver implements:
\begin{itemize}
\item The \code{open()} and \code{close()} system calls to
diff --git a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
index a79b11c..5c84850 100644
--- a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
+++ b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
@@ -35,7 +35,7 @@
\begin{frame}
\frametitle{No C library}
\begin{itemize}
- \item The kernel has to be standalone and can't use user-space code.
+ \item The kernel has to be standalone and can't use user space code.
\item User space is implemented on top of kernel services, not the
opposite.
\item Kernel code has to supply its own library implementations
@@ -82,7 +82,7 @@
\item They are related to the emulation of floating point
operation performed by the user space applications, triggering
an exception into the kernel.
- \item Using soft-float, i.e. emulation in user-space, is however
+ \item Using soft-float, i.e. emulation in user space, is however
recommended for performance reasons.
\end{itemize}
\end{itemize}
@@ -241,7 +241,7 @@
\begin{frame}
\frametitle{User space device drivers 1/2}
\begin{itemize}
- \item Possible to implement device drivers in user-space!
+ \item Possible to implement device drivers in user space!
\item Such drivers just need access to the devices through minimum,
generic kernel drivers.
\item Examples
diff --git a/slides/sysdev-block-filesystems/journal.dia b/slides/sysdev-block-filesystems/journal.dia
index 2cb7a24..48c36ba 100644
--- a/slides/sysdev-block-filesystems/journal.dia
+++ b/slides/sysdev-block-filesystems/journal.dia
@@ -430,7 +430,7 @@ in the journal#</dia:string>
<dia:attribute name="text">
<dia:composite type="text">
<dia:attribute name="string">
- <dia:string>#User-space#</dia:string>
+ <dia:string>#User space#</dia:string>
</dia:attribute>
<dia:attribute name="font">
<dia:font family="sans" style="0" name="Helvetica"/>
diff --git a/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex b/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
index 29729f2..2c1dfb8 100644
--- a/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
+++ b/slides/sysdev-linux-intro-features/sysdev-linux-intro-features.tex
@@ -134,7 +134,7 @@
\frametitle{Virtual filesystems}
\begin{itemize}
\item Linux makes system and kernel information available in
- user-space through virtual filesystems.
+ user space through virtual filesystems.
\item Virtual filesystems allow applications to see directories and
files that do not exist on any real storage: they are created on the
fly by the kernel
diff --git a/slides/sysdev-realtime/sysdev-realtime.tex b/slides/sysdev-realtime/sysdev-realtime.tex
index 6a681c2..9d72c7e 100644
--- a/slides/sysdev-realtime/sysdev-realtime.tex
+++ b/slides/sysdev-realtime/sysdev-realtime.tex
@@ -89,8 +89,8 @@
\item An event from the physical world happens and gets notified
to the CPU by means of an interrupt
\item The interrupt handler recognizes and handles the event, and
- then wake-up the user-space task that will react to this event
- \item Some time later, the user-space task will run and be able to
+ then wake-up the user space task that will react to this event
+ \item Some time later, the user space task will run and be able to
react to the physical world event
\end{itemize}
\item Real-time is about providing guaranteed worst case latencies
@@ -176,7 +176,7 @@
\frametitle{Understanding preemption (1)}
\begin{itemize}
\item The Linux kernel is a preemptive operating system
- \item When a task runs in user-space mode and gets interrupted by an
+ \item When a task runs in user space mode and gets interrupted by an
interruption, if the interrupt handler wakes up another task, this
task can be scheduled as soon as we return from the interrupt
handler.
@@ -404,7 +404,7 @@
\item Hardware timers are multiplexed, so that a single hardware
timer is sufficient to handle a large number of
software-programmed timers.
- \item Usable directly from user-space using the usual timer APIs
+ \item Usable directly from user space using the usual timer APIs
\end{itemize}
\end{itemize}
\end{frame}
@@ -1069,7 +1069,7 @@ echo 0 > /sys/kernel/debug/tracing/tracing_enabled
\begin{itemize}
\item Factored real-time core with skins implementing various
real-time APIs
- \item Seamless support for hard real-time in user-space
+ \item Seamless support for hard real-time in user space
\item No second-class citizen, all ports are equivalent feature-wise
\item Xenomai support is as much as possible independent from the
Linux kernel version (backward and forward compatible when
@@ -1082,9 +1082,9 @@ echo 0 > /sys/kernel/debug/tracing/tracing_enabled
\end{frame}
\begin{frame}
- \frametitle{Xenomai user-space real-time support}
+ \frametitle{Xenomai user space real-time support}
\begin{itemize}
- \item Xenomai supports real-time in user-space on 5 architectures,
+ \item Xenomai supports real-time in user space on 5 architectures,
including 32 and 64 bits variants.
\item Two modes are defined for a thread
\begin{itemize}
@@ -1176,9 +1176,9 @@ echo 0 > /sys/kernel/debug/tracing/tracing_enabled
\end{frame}
\begin{frame}
- \frametitle{Xenomai user-space support}
+ \frametitle{Xenomai user space support}
\begin{itemize}
- \item User-space libraries are compiled using the traditional autotools
+ \item User space libraries are compiled using the traditional autotools
\begin{itemize}
\item \code{./configure --host=arm-linux && make && make DESTDIR=/your/rootfs/ install}
\end{itemize}
@@ -1261,8 +1261,8 @@ ret = bind(s, (struct sockaddr *)&saddr, sizeof(saddr));
\begin{itemize}
\item {\small
\url{http://xenomai.org/documentation/branches/v2.4.x/pdf/Native-API-Tour-rev-C.pdf}}
- \item Usable both in user-space and kernel space. Development of
- tasks in user-space is the preferred way.
+ \item Usable both in user space and kernel space. Development of
+ tasks in user space is the preferred way.
\item More coherent and more flexible API than the POSIX
API. Easier to learn and understand. Certainly the way to go for
new applications.
diff --git a/slides/sysdev-udev/sysdev-udev.tex b/slides/sysdev-udev/sysdev-udev.tex
index 0e4a738..56eb101 100644
--- a/slides/sysdev-udev/sysdev-udev.tex
+++ b/slides/sysdev-udev/sysdev-udev.tex
@@ -35,7 +35,7 @@
\begin{frame}[fragile]
\frametitle{Starting udev (1)}
\begin{itemize}
- \item At the very beginning of user-space startup,
+ \item At the very beginning of user space startup,
mount the \code{/dev/} directory as a \code{tmpfs} filesystem:\\
\code{sudo mount -t tmpfs udev /dev}
\item \code{/dev/} is populated with static devices available in
More information about the training-materials-updates
mailing list