Merge branch 'master' of git.martlubbers.net:msc-thesis1617

[msc-thesis1617.git] / conclusion.tex

diff --git a/conclusion.tex b/conclusion.tex
index de3da6c..94b75ff 100644 (file)
--- a/conclusion.tex
+++ b/conclusion.tex
@@ -25,7 +25,7 @@ broken device without needing to recompile the code.
 
 \section{Discussion}
 \todo{class based shallow doesn't have multiple backend support}
 
 \section{Discussion}
 \todo{class based shallow doesn't have multiple backend support}

-\todo{slow client software because of intepretation}
+\todo{slow client software because of interpretation}

 \todo{What happens if a device dies? Task resending, add to handshake}
 
 
 \todo{What happens if a device dies? Task resending, add to handshake}
 
 


@@ -56,6 +56,8 @@ of the client software. However, it could be implemented as a compile-time
 option and exchanged during the handshake so that the server knows the
 multithreading capabilities of the client.
 
 option and exchanged during the handshake so that the server knows the
 multithreading capabilities of the client.
 

+\todo{Parametric lenses on devices share?}
+

 \subsection{Resources}
 Resource analysis during compilation can be useful to determine if an
 \gls{mTask}-\gls{Task} is suitable for a specific device. If the device does
 \subsection{Resources}
 Resource analysis during compilation can be useful to determine if an
 \gls{mTask}-\gls{Task} is suitable for a specific device. If the device does


@@ -65,7 +67,7 @@ given.
 
 This idea could be extended to the analysis of stack size and possibly
 communication bandwidth. With this functionality ever more reliable fail-over
 
 This idea could be extended to the analysis of stack size and possibly
 communication bandwidth. With this functionality ever more reliable fail-over

-systems can be designed. When the system knows more precise bounds it can
+systems can be designed. When the system knows preciser bounds it can

 allocate more \glspl{Task} on a device whilst staying within safe memory
 bounds. The resource allocation can be done at runtime within the backend
 itself or a general backend can be devices that can calculate the resources
 allocate more \glspl{Task} on a device whilst staying within safe memory
 bounds. The resource allocation can be done at runtime within the backend
 itself or a general backend can be devices that can calculate the resources