This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Triton-private Repository". The branch, master has been updated via d71cd4c41957356f20cd8043238609b0d629b8a2 (commit) via 1b8b991a7b1cfe8675f5113c8b788fab52b63c54 (commit) via 745ae78939aac89e98bf8a3ec8e2de1652ee19cc (commit) via a05c5e60bb6427018f676acab8be4a6e85bb7f35 (commit) via 4f75fa6b9d5e319a1fac5d722c6cf0aee1d77eb9 (commit) from 8b83dbc762d6ba7de8b394c18d223e0ec58b2118 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit d71cd4c41957356f20cd8043238609b0d629b8a2 Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 16:44:58 2012 -0500 clarify system software commit 1b8b991a7b1cfe8675f5113c8b788fab52b63c54 Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 16:44:49 2012 -0500 Restore pmccabe tool citation commit 745ae78939aac89e98bf8a3ec8e2de1652ee19cc Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 16:44:29 2012 -0500 Restart DB section for now commit a05c5e60bb6427018f676acab8be4a6e85bb7f35 Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 16:44:14 2012 -0500 Make inline code macro use a plain font commit 4f75fa6b9d5e319a1fac5d722c6cf0aee1d77eb9 Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 15:23:11 2012 -0500 Add code repo link ----------------------------------------------------------------------- Summary of changes: papers/2011/aesop/aesop.tex | 3 ++- papers/2011/aesop/conclusion.tex | 8 ++++++-- papers/2011/aesop/context.tex | 2 ++ papers/2011/aesop/evaluation.tex | 2 +- papers/2011/aesop/implementation.tex | 4 ++-- papers/2011/aesop/intro.tex | 3 ++- 6 files changed, 15 insertions(+), 7 deletions(-) Diff of changes: diff --git a/papers/2011/aesop/aesop.tex b/papers/2011/aesop/aesop.tex index 996c862..ac273ef 100644 --- a/papers/2011/aesop/aesop.tex +++ b/papers/2011/aesop/aesop.tex @@ -51,7 +51,8 @@ xleftmargin=6ex \hyphenation{op-tical net-works semi-conduc-tor} \DeclareRobustCommand{\code}[1] - {\lstinline[breaklines=true,basicstyle=\ttfamily]{#1}} + {\lstinline[breaklines=true,basicstyle=\ttfamily, + keywordstyle=,identifierstyle=]{#1}} %\newcommand{\todo}[1]{ {\textcolor{red} { TODO: #1 }}} \newcommand{\woz} [1] {\todo{ Wozniak: #1 }} diff --git a/papers/2011/aesop/conclusion.tex b/papers/2011/aesop/conclusion.tex index 51de97f..d78a12a 100644 --- a/papers/2011/aesop/conclusion.tex +++ b/papers/2011/aesop/conclusion.tex @@ -22,8 +22,9 @@ concurrent execution paths to dedicated operating system threads. When considering programmer productivity, \aesop performs equally well, mainly because it has been specifically designed to implement highly scalable distributed services. It reduces code complexity while also -offering advanced primitives such as cancellation of execution paths and -control of variable scope that are not available in any other system software +offering advanced primitives such as cancellation of execution paths +% and control of variable scope +that are not available in any other system software development environment. We will continue to evaluate and evolve the \aesop language as we use it @@ -33,6 +34,9 @@ One example, which exists in prototype form already, is a remote procedure call framework that uses \aesop to manage concurrent communication, timeout, and retry functionality in a transparent manner. We also plan to provide enhanced functionality for debugging \aesop functions. +\aesop, and the code used to evaluate its performance, is available online at +\url{http://trac.mcs.anl.gov/projects/aesop}. + %- Need to fix some parser issues %- Compilation speed diff --git a/papers/2011/aesop/context.tex b/papers/2011/aesop/context.tex index 5f22e15..ca11583 100644 --- a/papers/2011/aesop/context.tex +++ b/papers/2011/aesop/context.tex @@ -289,6 +289,8 @@ Databases are commonly used for file system metadata, where efficiency is critical. Berkeley~DB~\cite{BDB_1999} does not provide a nonblocking API, but wrapper libraries have been used to achieve this. Postgres offers an asynchronous interface~\cite{postgresAsync} in its C API. + + %that allows database %operations to be posted asynchronously; a separate library function tests %whether a diff --git a/papers/2011/aesop/evaluation.tex b/papers/2011/aesop/evaluation.tex index 27c4f0f..c8ccda3 100644 --- a/papers/2011/aesop/evaluation.tex +++ b/papers/2011/aesop/evaluation.tex @@ -259,7 +259,7 @@ Table~\ref{tab:complexity} compares the code complexity of each server implemenation using McCabe Cyclomatic Complexity (CC)~\cite{mccabe}, Modified McCabe Cyclomatic Complexity (mod. CC), and Source Lines of Code (SLOC). The CC and Mod. CC metrics were measured by -using the pmccabe tool, version 2.6, created by Paul Bame\begin{comment}~\cite{pmccabe}\end{comment}; +using the pmccabe tool, version 2.6, created by Paul Bame~\cite{pmccabe}; the SLOC metrics were measured using the sloccount tool, version 2.26, created by David A. Wheeler\begin{comment}~\cite{sloccount}\end{comment}. diff --git a/papers/2011/aesop/implementation.tex b/papers/2011/aesop/implementation.tex index 46c84a7..d78fae6 100644 --- a/papers/2011/aesop/implementation.tex +++ b/papers/2011/aesop/implementation.tex @@ -8,7 +8,7 @@ Since \aesop implements an extension to the C language, all valid C programs are also valid \aesop programs, and all C features can be used within an \aesop program. Currently, the translator needs to rewrite only \code{aesop} functions; all other code is passed through unmodified. - +% \begin{figure} %\vskip -0.25in \centering @@ -16,7 +16,7 @@ functions; all other code is passed through unmodified. \caption{Model of Aesop usage.\label{fig:model}} \vspace{-.2in} \end{figure} - +% Figure~\ref{fig:model} shows how an \code{aesop} function, \code{service_function}, is translated by the current version of the \aesop translator. As a first step, all \code{aesop} diff --git a/papers/2011/aesop/intro.tex b/papers/2011/aesop/intro.tex index 1bac600..bc63da0 100644 --- a/papers/2011/aesop/intro.tex +++ b/papers/2011/aesop/intro.tex @@ -26,7 +26,8 @@ in between. In some cases, the most efficient API is platform specific. This diversity makes it difficult to build algorithms that are portable and yet capable of leveraging each component in an optimal manner. -The two most common models for managing asynchronous activity are +The two most common models for managing asynchronous activity in system +software are multithreading and event-driven architectures. Examples of both can be found in various large-scale production services. The Apache web server advocates a multithreaded mode of operation for high-performance hooks/post-receive -- Triton-private Repository