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 fb4b88cb2f3024332b83e09411202ba2ec17b1ce (commit) from 0875683647b47cc9a2bf5ac4350d80f564cea944 (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 fb4b88cb2f3024332b83e09411202ba2ec17b1ce Author: Dries Kimpe <[email protected]> Date: Fri Mar 16 13:55:58 2012 -0500 model fixes ----------------------------------------------------------------------- Summary of changes: papers/2011/aesop/model.tex | 14 ++++++++------ 1 files changed, 8 insertions(+), 6 deletions(-) Diff of changes: diff --git a/papers/2011/aesop/model.tex b/papers/2011/aesop/model.tex index 247a2f6..5d54492 100644 --- a/papers/2011/aesop/model.tex +++ b/papers/2011/aesop/model.tex @@ -114,7 +114,7 @@ language, a proper \code{aesop} function should return as soon as possible when a branch is in a cancelled state. % when to use blocking functions -The intention is that functions that are not completely cpu-bound +The intention is that functions that are not completely CPU-bound (i.e., cannot efficiently fully consume a thread) are to be \code{aesop} functions. \aesop detects when a \code{aesop} function can no longer make progress (for example, because the function is waiting @@ -186,7 +186,7 @@ to a request, cancelling the request when the allocated time is exceeded. In the code example, \code{write} concurrently forwards the write operation to -\code{REPLICAS} replicas. This is done using a for loop containing a pbranch. +\code{REPLICAS} replicas. This is implemented using a \code{for} loop containing a pbranch. Since the pbranch statement does not wait for the completion of the branch, the next iteration of the \code{for} loop can start before the previous one completed. In \code{replicateWrite}, a common pattern for easily handling @@ -197,13 +197,15 @@ branch. Thus, if \code{doReplicateWrite} (line 15) completes first, the operation completed within the allocated time frame, and the timer (line 4) will be cancelled. However, if line 15 takes longer than \code{TIMEOUT} to complete, the timer (line 11) will complete first, causing the ongoing -\code{doReplicaWrite} operation to be cancelled. Note how \code{replicaWrite}, +\code{doReplicaWrite} operation to be cancelled. The \code{ae_cancel_branches} +call internally synchronizes, preventing both branches from cancelling each +other. Note how \code{replicaWrite}, in a straightforward and reusable manner, adds a time-out to the existing \code{doReplicaWrite} call. -The short code fragment from listing~\ref{lst:parallelfor} effectively -implemented the pattern shown in Figure~\ref{fig:sm}, in which a number of +The short code fragment from Listing~\ref{lst:parallelfor} +implements the pattern shown in Figure~\ref{fig:sm}, in which a number of concurrent write operations are started; each consists of three tasks that -can be executed concurrently, and each write operation is protected by a timeout. +can be executed concurrently, with each write operation protected by a timeout. hooks/post-receive -- Triton-private Repository