Changes between Version 13 and Version 14 of AppMultiThread

Timestamp:

Mar 7, 2008, 8:12:07 AM (17 years ago)

Author:

davea

Comment:

--

AppMultiThread

@@ -21 +21 @@
 == Assumptions ==
 
-We assume that applications have the following properties:
-
- * Given a number of CPUs N, the app can select a number of threads so that it uses N CPUs as fully as possible.  This number may be less than or greater than N; it may be 1.
- * There may be periods during the app's execution during which its number of threads becomes less than N; e.g. there may be periods during which the app is not parallel, and the number of threads becomes 1.
+We assume that an app version has a parameter Nthreads,
+the maximum number of threads it uses.
+The scheduler sends a host the app version for which Nthreads <= NCPUS and is greatest.
 
 == Scheduling policy ==
@@ -39 +38 @@
 Our scheduling policy, given N CPUs, is:
 
- * Instruct applications to use enough threads for N CPUs, and monitor how many threads NT(A) they actually use.
  * Given a set of runnable applications A1, A2 (ordered by priority or deadline), run applications until the number of actual threads exceeds N.
- * Reschedule the CPUs whenever NT(A) changes for a running app A.
-
 
 == API ==
@@ -73 +69 @@
  * <ncpus_available>
 
-Shared-memory messages:
- * core->app (process control channel): {{{<ncpus_available>}}}
- * app->core (process control channel): {{{<nthreads>}}}
-
 State:
  * int ACTIVE_TASK::nthreads