[Swift-commit] r2409 - text/hpdc09submission

[noreply at svn.ci.uchicago.edu]

Author: benc
Date: 2009-01-09 03:23:32 -0600 (Fri, 09 Jan 2009)
New Revision: 2409

Modified:
   text/hpdc09submission/paper.latex
Log:
capitalise Swift

Modified: text/hpdc09submission/paper.latex
===================================================================
--- text/hpdc09submission/paper.latex	2009-01-09 09:19:18 UTC (rev 2408)
+++ text/hpdc09submission/paper.latex	2009-01-09 09:23:32 UTC (rev 2409)
@@ -125,7 +125,7 @@
 model for representing collections of files and directories that are
 passed to Swift procedures, and a mapping model to convert between the
 physical representation of data on storage systems and the logical
-representation of data structures in the abstract swift programming
+representation of data structures in the abstract Swift programming
 model.
 
 Swift itself does not specify how the physical data environment is
@@ -144,7 +144,7 @@
 
 Swift is implemented by compiling to a Karajan program, which provides
 several benefits. A notable benefit visible to users is that of
-providers. This enbles the swift execution model to be extended by
+providers. This enbles the Swift execution model to be extended by
 adding new data providers and job execution providers. This is
 explained in more detail in section X: Swift Implementation.
 
@@ -180,7 +180,7 @@
 that an output variable of one function is passed as the input
 variable to the second function.
 
-This dataflow model means that within a swift program, functions are
+This dataflow model means that within a Swift program, functions are
 executed when their data is available - which is not necessarily in
 source-code order.
 
@@ -731,7 +731,7 @@
 \subsection{Executing on a remote site}
 
   With the above restrictions, execution of a unix program on a remote
-site is straightforward. The swift runtime must prepare a remote
+site is straightforward. The Swift runtime must prepare a remote
 working directory for each job with appropriate input files staged in;
 then it must execute the program; and then it must stage the output
 files back out the submitting system. The site model used by Swift is
@@ -785,7 +785,7 @@
 case exectuion will be attemted on all sites. In the presence of
 multiple sites, it is necessary to choose between the avalable sites.
 The Swift \emph{site selector} achivees this by maintaining a score for
-each site which determines the load that swift will place on that site.
+each site which determines the load that Swift will place on that site.
 As a site is successful in executing jobs, this score wil be increased
 and as the site is uncsuccessful, this score will be cdecreased. In
 addition to selecting between sites, this mechanism provides some
@@ -925,8 +925,8 @@
 \section{Example applications}
 
 TODO: two or three applications in brief. discuss both the application
-behaviour in relation to swift, but underlying grid behaviour in
-relation to swift
+behaviour in relation to Swift, but underlying grid behaviour in
+relation to Swift
 
 One app: CNARI + TeraGrid - small jobs (3s), many of them.
 
@@ -1205,15 +1205,15 @@
 \cite{LONIPIPELINE}
 \subsection{The IBM BG/P}
 
-  TODO: interesting from swift perspective:
+  TODO: interesting from Swift perspective:
 
   1. getting things running at all: use of BG/P for loosely coupled
 tasks, which is a somewhat untraditional use of such a machine; lack of
 antive LRM that is anywhere near appropraite for that (pset granularity
 only, and only running one executable) - falkon as solution to this;
 
-decomposition of large machine into multiple swift sites, with 1 pset =
-1 swift site - how some of the problems related to running on multisite
+decomposition of large machine into multiple Swift sites, with 1 pset =
+1 Swift site - how some of the problems related to running on multisite
 grids are sort-of similar to problems within the BG/P - hierarchical
 scheduling of of jobs and hierarchical management of data.
 
@@ -1258,7 +1258,7 @@
 
 \section{Implementation status}
 
-  TODO: list how swift can be downloaded here. describe development group?
+  TODO: list how Swift can be downloaded here. describe development group?
 
 active development group; releases roughly every 2 months.
 
@@ -1398,7 +1398,7 @@
 people who have thus far contributed directly to this written paper:
 me, wilde
 
-people who have thus far contributed to the swift work described here:
+people who have thus far contributed to the Swift work described here:
 Swift core: me, wilde, hategan, milena, yong, ian
 CNARI: skenny
 OSG: mats