If we actually want to have a code segment, would it make sense to have some sort of plug-in concept (dlopen()) such that the projects don't have to hack the BOINC scheduler source code to get their app_plan() function into the scheduler?
Best, Bernd David Anderson wrote, On 22.07.2009 0:58 Uhr: > The app_plan() function can do whatever you want, > including reading parameters from a database. > For me, it's simpler to have the parameters in the code. > > -- David > > Oliver Bock wrote: > >> What's the rationale behind that decision? If your concern is that even more >> DB fetches might hurt the scheduler's performance one could instead use some >> kind of config file. Of course one should put the *logic* into the code but >> not >> necessarily the config values to tune the logic, right? I can think of a >> number >> of individual "cuda" plan classes that only vary slightly in their >> particular >> configuration (e.g. required global memory), not in their general logic. >> > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
