Changes between Version 5 and Version 6 of AppMultiThread

Timestamp:

Nov 20, 2007, 2:30:44 PM (17 years ago)

Author:

Nicolas

Comment:

m

AppMultiThread

@@ -53 +53 @@
 }}}
 
-An application calls boinc_target_nthreads() periodically,
+An application calls {{{boinc_target_nthreads()}}} periodically,
 at points where it is able to change its number of threads.
-It calls boinc_actual_nthreads() to report its actual number of threads.
+It calls {{{boinc_actual_nthreads()}}} to report its actual number of threads.
 
 A WU DB record can specify "max average ncpus",
 an estimate of Ncpus(A) on a host with arbitrarily many CPUs.
-This is used
-by the client and scheduler to estimate completion time.
+This is used by the client and scheduler to estimate completion time.
 
 == Implementation ==
 
 Shared-memory messages:
- * core->app (process control channel): <target_nthreads>
- * app->core (process control channel): <actual_nthreads>
+ * core->app (process control channel): {{{<target_nthreads>}}}
+ * app->core (process control channel): {{{<actual_nthreads>}}}
 
-Client maintains estimates of CPU effiency per job,
-uses this to scale target_nthreads.
+Client maintains estimates of CPU efficiency per job,
+uses this to scale {{{target_nthreads}}}.
 
 
-Implementation (enforce_schedule()):
-as we schedule jobs, decrement CPU count by scaled actual_nthreads.
-rr_simulation() needs to be modified too.
+Implementation ({{{enforce_schedule()}}}):
+as we schedule jobs, decrement CPU count by scaled {{{actual_nthreads}}}.
+{{{rr_simulation()}}} needs to be modified too.