Changes between Version 32 and Version 33 of AppMultiThread

Timestamp:

Jun 6, 2012, 11:16:27 AM (13 years ago)

Author:

davea

Comment:

--

AppMultiThread

@@ -39 +39 @@
 and setThreadPriority() is then called by each worker thread.
 
-== Deploying a multicore app version ==
+== Specifying a plan class ==
 
-BOINC uses the [AppPlan application planning] mechanism to
-coordinate the scheduling of multicore applications.
+Multicore apps must the [AppPlan plan class] mechanism to
+specify their properties.
+You may be able to use the [AppPlan predefined "mt" class].
+Otherwise you must specify your own,
+using either [AppPlanSpec XML] or [PlanClassFunc C++].
 
-Suppose you've developed a multicore program,
-and that it achieves a linear speedup on up to 64 processors, and no additional speedup beyond that.
-To deploy it:
-
- * Choose a "plan class" name for the program, say "mt" (see below).
- * Create an [AppVersionNew app version], specifying its plan class as "mt".
- * Edit the following in sched/sched_customize.cpp if needed:
-{{{
-// the following is for an app that can use anywhere from 1 to 64 threads
-//
-static inline bool app_plan_mt(
-    SCHEDULER_REQUEST& sreq, HOST_USAGE& hu
-) {
-    double ncpus = g_wreq->effective_ncpus;
-        // number of usable CPUs, taking user prefs into account
-    int nthreads = (int)ncpus;
-    if (nthreads > 64) nthreads = 64;
-    hu.avg_ncpus = nthreads;
-    hu.max_ncpus = nthreads;
-    sprintf(hu.cmdline, "--nthreads %d", nthreads);
-    hu.projected_flops = sreq.host.p_fpops*hu.avg_ncpus*.99;
-        // the .99 ensures that on uniprocessors a sequential app
-        // will be used in preferences to this
-    hu.peak_flops = sreq.host.p_fpops*hu.avg_ncpus;
-    return true;
-}
-
-}}}