update

diff --git a/talk.tex b/talk.tex
index 57be54971b93ef7c1898cc0e36a7a60eaaaae47f..75bdba14bb6f4bf3b4ea9f41f56928106390a9a3 100644 (file)
--- a/talk.tex
+++ b/talk.tex
@@ -203,6 +203,7 @@
        \begin{itemize}
                \item Remove obselete page flipping mode (\brev{289583})
                \item Implement multiqueue (\brev{294442})
+               \item Throughput from guest to host: 1 queue 5.8 Gb/s, 4 queues 11.2 Gb/s
        \end{itemize}
     \end{itemize}
 \end{frame}
@@ -219,17 +220,6 @@
        \item purge unused page flipping mode to simplify code
        \item low hanging fruit, multiqueue, turns out not so low-hanging
        \item rewrite large part of netfront.c
-    \end{itemize}
-}
-
-\begin{frame}
-    \frametitle{xen-net related improvements}
-    \begin{itemize}
-        \item graph for netfront throughput
-    \end{itemize}
-\end{frame}
-\note{
-    \begin{itemize}
         \item doesn't scale linearly yet, likely to be bottleneck in Xen
        \item room to optimise single stream throughput
        \item tests run with WITNESS enabled
@@ -237,7 +227,10 @@
     \end{itemize}
 }
 
-\section{Xen}
+
+\section{News from Xen}
+
+\subsection{xen_up}
 
 \begin{frame}
     \frametitle{The full virtualization spectrum}
@@ -497,11 +490,22 @@ ows, FreeBSD)
 \begin{frame}
     \frametitle{xSplice - hypervisor hot-patching}
     \begin{itemize}
-        \item ABC
+       \item Rationale:
+       \begin{itemize}
+               \item Rebooting hypervisor to fix security bugs are not desirable
+               \item A large number of security bugs require very simple patch to fix
+       \end{itemize}
+       \item Phase one goal is to handling patching functions, patching structure is yet to come
+       \item User space tooling is not tied to particular operating system
     \end{itemize}
 \end{frame}
 \note{
     \begin{itemize}
+       \item cause disruption for users
+       \item for very large installation base, rebooting within the time frame that required by Xen project security process is not always feasible
+       \item some organisations developed their own hot-patching. this risks fragmenting the community
+       \item members of Xen project realised this and started to push for upstream effort for hypervisor hot-patching
+
     \end{itemize}
 }