Tracked down the two figures needed in the routing documentation.
authorakhi akhi@inf.ethz.ch <akhi akhi@inf.ethz.ch>
Tue, 30 Aug 2011 09:54:09 +0000 (11:54 +0200)
committerakhi akhi@inf.ethz.ch <akhi akhi@inf.ethz.ch>
Tue, 30 Aug 2011 09:54:09 +0000 (11:54 +0200)
doc/006-routing/Routing.tex
doc/006-routing/overview_multihop_channel.dia [new file with mode: 0644]
doc/006-routing/overview_multihop_channel.pdf [new file with mode: 0644]
doc/006-routing/vcis.dia [new file with mode: 0644]
doc/006-routing/vcis.pdf [new file with mode: 0644]

index 4fd31bd..c706f2c 100644 (file)
@@ -148,12 +148,12 @@ In addition to the forwarding table, each node maintains a routing table. The ro
 
 The virtual circuit switching approach would also allow to reserve some resources on the nodes for each channel. Per-channel reserved resources could include buffer space to save received, but not yet forwarded messages, or bandwidth on the ICD links. This is potentially very useful for congestion and flow control. Note that we cannot simply drop messages in case of congested links, as we want to provide a reliable messaging service. As of now, we do not reserve resources on the nodes, but allocate required resources dynamically.
 
-%% \begin{figure}[h]
-%%     \begin{center}
-%%     \includegraphics[scale=0.7]{overview_multihop_channel.pdf}
-%%     \caption{Basic set-up}\label{fig:multihop-chan}
-%%     \end{center}
-%% \end{figure}
+\begin{figure}[h]
+       \begin{center}
+       \includegraphics[scale=0.7]{overview_multihop_channel.pdf}
+       \caption{Basic set-up}\label{fig:multihop-chan}
+       \end{center}
+\end{figure}
 
 \section{Additional monitor bindings}
 A multi-hop channel is multiplexed over the available ICD links. However, for each multi-hop channel, there will be two additional ICD links: Two additional LMP channels will be created between the client's dispatcher and the monitor running on its core and between the service's dispatcher and the monitor on its core. LMP channels are rather cheap - they do not require polling and require only a small amount of memory. Therefore, this does not compromise our goal of optimizing resource usage. Figure~\ref{fig:multihop-chan} shows an example set-up of a multi-hop channel with the two additional LMP channels. 
@@ -171,12 +171,12 @@ An attacker sending messages with manipulated virtual circuit identifiers may be
 
 This design requires that each node on a multi-hop channel tells its neighbours what virtual circuit identifier they should use for messages sent over that particular channel. This happens in the set-up phase of a multi-hop channel (see section~\ref{section: set-up}).
 
-%% \begin{figure}[h]
-%%     \begin{center}
-%%     \includegraphics[scale=0.68]{vcis.pdf}
-%%     \caption{Virtual circuit identifiers} \label{fig:vci}
-%%     \end{center}
-%% \end{figure}
+\begin{figure}[h]
+       \begin{center}
+       \includegraphics[scale=0.68]{vcis.pdf}
+       \caption{Virtual circuit identifiers} \label{fig:vci}
+       \end{center}
+\end{figure}
 
 
 \section{Channel set-up}
diff --git a/doc/006-routing/overview_multihop_channel.dia b/doc/006-routing/overview_multihop_channel.dia
new file mode 100644 (file)
index 0000000..03c520a
Binary files /dev/null and b/doc/006-routing/overview_multihop_channel.dia differ
diff --git a/doc/006-routing/overview_multihop_channel.pdf b/doc/006-routing/overview_multihop_channel.pdf
new file mode 100644 (file)
index 0000000..bf61f29
Binary files /dev/null and b/doc/006-routing/overview_multihop_channel.pdf differ
diff --git a/doc/006-routing/vcis.dia b/doc/006-routing/vcis.dia
new file mode 100644 (file)
index 0000000..de87104
Binary files /dev/null and b/doc/006-routing/vcis.dia differ
diff --git a/doc/006-routing/vcis.pdf b/doc/006-routing/vcis.pdf
new file mode 100644 (file)
index 0000000..af1daf1
Binary files /dev/null and b/doc/006-routing/vcis.pdf differ