diff --git a/slides/networking-stack-overview/networking-stack-overview.tex b/slides/networking-stack-overview/networking-stack-overview.tex index 7bdfd7b9bb..b4c6101a28 100644 --- a/slides/networking-stack-overview/networking-stack-overview.tex +++ b/slides/networking-stack-overview/networking-stack-overview.tex @@ -166,13 +166,13 @@ \section{Introduction - Networking Technologies} \begin{itemize} \item A 802.1Q frame has included an extra \textbf{4 bytes} tag in the Ethernet header \item The \textbf{ethertype} is set to \code{0x8100}, the real ethertype is stored after the tag - \item A 16 bits value identifies the Tag : \textbf{T}ag \textbf{C}ontrol \textbf{I}nformation + \item A 16-bit value identifies the Tag : \textbf{T}ag \textbf{C}ontrol \textbf{I}nformation \begin{itemize} \item 3 bits indicate a \textbf{priority}, between 0 and 7 \begin{itemize} \item Also called \textbf{C}lass \textbf{o}f \textbf{S}ervice \end{itemize} - \item 1 bit \textbf{D}rop \textbf{E}ligible \textbf{I}ndicator + \item 1 bit for the \textbf{D}rop \textbf{E}ligible \textbf{I}ndicator \item 12 bits represent the ID of the vlan, between 1 and 4094 \begin{itemize} \item ID 0 means \textbf{no tag}, only the priority is considered @@ -190,7 +190,7 @@ \section{Introduction - Networking Technologies} \item Defined by \textbf{subnets}, linked tothegher by \textbf{routers} \item Main technologies are \textbf{IPv4} and \textbf{IPv6} \begin{itemize} - \item IPv4 : 32-bits addresses, IPv6 : 128-bits addresses + \item IPv4 : 32-bit addresses, IPv6 : 128-bit addresses \end{itemize} \item Layer 2 to Layer 3 addresses can be associated \begin{itemize} @@ -244,7 +244,7 @@ \section{Introduction - Networking Technologies} \begin{itemize} \item \textit{e.g.} Wireguard Encrypts and encapsulates IP packets into UDP packets \end{itemize} - \item There may therefore be more headers to decapsulate than there are ISO layers + \item There may therefore be more headers to decapsulate than there are OSI layers \end{itemize} \end{columns} \end{frame} @@ -355,7 +355,7 @@ \section{The Linux Kernel Networking Stack} \item Ethernet PHYs are supported via \href{https://docs.kernel.org/networking/phy.html}{phylib}, and the MAC to PHY link via \href{https://docs.kernel.org/networking/sfp-phylink.html}{phylink} \item SFF and SFP cages and modules are also supported \item Supports 802.3 frames and Ethernet II - \item Multiple 802.1 and 802.3 Low-Level aspects are supported : + \item Multiple 802.1 and 802.3 low-level aspects are supported : \begin{itemize} \item Vlan with 802.1Q and 802.1AD \item Bridging and Switching @@ -418,7 +418,7 @@ \section{The Linux Kernel Networking Stack} \begin{frame}{Userspace Networking} \begin{itemize} \item Userspace applications can also access traffic at various points in the stack through sockets : - \item \code{AF_PACKET} Sockets allow raw Layer 2 access + \item \code{AF_PACKET} sockets allow raw Layer 2 access \begin{itemize} \item Can be used for custom protocol support in userspace \item Used by \code{libpcap} and traffic monitoring tools like \textbf{tcpdump} and \textbf{wireshark} @@ -498,7 +498,6 @@ \section{The Linux Kernel Networking Stack} \item For \textbf{ongoing development}, to discuss current issues and future work \item Very technical topics \item Usually single-day track on a multi-day event - \item LPC 2025 will be in TĂ´kyo, Japan, in December \end{itemize} \item The \href{https://netdevconf.info/}{\textbf{Netdev Conference}} is dedicated to kernel networking development \begin{itemize} @@ -506,7 +505,6 @@ \section{The Linux Kernel Networking Stack} \item Hosted by a dedicated group of individuals (the Netdev Society) \item 4 or 5 days, mixing remote and on-site sessions \item Very technical topics as well, not many are embedded-oriented - \item Netdev 2025 was in Zagreb, Croatia, in April. \end{itemize} \end{itemize} \end{frame}