begin to write results

doc/Design.tex

@@ -187,8 +187,9 @@ correcting the carry.
 The benchmarks were performed on two hosts, a load generator and a
 nat64 translator. Both hosts were equipped with a dual port
 Intel X520 10 Gbit/s network card. Both hosts were connected using DAC
-without any equipment in between. Figure \ref{fig:softwarenat64design}
-shows the setup.
+without any equipment in between. TCP offloading was enabled in the
+X520 cards. Figure \ref{fig:softwarenat64design}
+shows the network setup.
 \begin{figure}[h]
   \includegraphics[scale=0.5]{softwarenat64design}
   \centering
@@ -202,6 +203,10 @@ generator is equipped with a quad core CPU (Intel(R) Core(TM) i7-6700
 CPU @ 3.40GHz), enabled with hyperthreading and 16 GB RAM. The NAT64
 translator is also equipped with a quard core CPU (Intel(R) Core(TM)
 i7-4770 CPU @ 3.40GHz) and 16 GB RAM.
+
+The first 10 seconds of the benchmark were excluded to avoid the tcp
+warm up phase.\footnote{iperf -O 10 parameter}
+
 \begin{figure}[h]
   \includegraphics[scale=0.5]{netpfgadesign}
   \centering

doc/Results.tex

@@ -12,7 +12,7 @@ objective of this thesis was to demonstrate the high speed
 capabilities of NAT64 in hardware, no benchmarks were performed on the
 P4 software implementation.
 % ----------------------------------------------------------------------
-\section{\label{results:p4}NAT64 with P4}
+\section{\label{results:p4}NAT64 Overview}
 We successfully implemented P4 code to realise
 NAT64\cite{schottelius:thesisrepo}. It contains parsers
 for all related protocols (ipv6, ipv4, udp, tcp, icmp, icmp6, ndp,
@@ -27,28 +27,53 @@ achieved bandwidths of the NAT64 solutions.
 
 \begin{table}[htbp]
 \begin{center}\begin{minipage}{\textwidth}
-\begin{tabular}{| c | p{130pt} | l |}
+\begin{tabular}{| c | c | c | c |}
 \hline
-Solution & Column 2 \newline (additional line) & Column 3 \\
+Solution & \multicolumn{3}{|c|}{Parallel connections} \\
+ & 1 & 20 & 3 \\
 \hline
-Tayga & C2,R2 & C2,R3 \\
+Tayga & 3.02 & 3.28  & 2.85\\
 \hline
-Jool	& \multicolumn{2}{| c |}{C2\&C3,R3} \\
+Jool & 6.67  & 16.8 ??  & 20.5 udp?\\
 \hline
-P4 / NetPFGA & C2,R4\footnote{Footnote to table~\ref{tab:benchmark}} & C3,R4\\
+P4 / NetPFGA & 9.28 & 9.29  & 9.29\\
 \hline
 \end{tabular}
 \end{minipage}
-\caption{Table 1}
-\label{tab:benchmark}
+\caption{NAT64 Benchmark (IPv6 initiating), all results in Gbit/sec (\%loss)}
+\label{tab:benchmarkv6}
 \end{center}
 \end{table}
 
 During the benchmarks the client
 
+\begin{table}[htbp]
+\begin{center}\begin{minipage}{\textwidth}
+\begin{tabular}{| c | c | c | c |}
+\hline
+Solution & \multicolumn{3}{|c|}{Parallel connections} \\
+ & 1 & 20 & 3 \\
+\hline
+Tayga & 3.36  & 3.29 & 3.11 \\
+\hline
+Jool	& 8.24  & 8.26 & 8.29\\
+\hline
+P4 / NetPFGA & 8.43 & 9.29  & 9.29\\
+\hline
+\end{tabular}
+\end{minipage}
+\caption{NAT64 Benchmark (IPv4 initiating), all results in Gbit/sec (\%loss)}
+\label{tab:benchmarkv4}
+\end{center}
+\end{table}
+
 
 % ----------------------------------------------------------------------
 \section{\label{Results:BMV2}BMV2}
+The software implementation of P4 features most features, which is
+mostly due to available externs that can checksum the payload: Acting
+as a ``proper'' participant in NDP, requires the host to calculate
+checksums over the payload.
 
 Responds to icmp, icmp6
 ndp \cite{rfc4861}
@@ -68,8 +93,7 @@ Stateful : no automatic removal
 
 % ----------------------------------------------------------------------
 \section{\label{results:tayga}Tayga}
-
-3gbit
+cpu bound, single thread
 
 % ----------------------------------------------------------------------