Hello
Based on my discussions with hkaiser, this is what I have understood.
There is a base class scheduler_base, for all scheduling policies. Now the
specific policies themselves, like local, priority_local, static etc. all
inherit this scheduler_base and have the functionality to create respective
executors (or something similar).
Apart from these, there is a factory class named scheduler_factory, which
returns an instance of one of the derived classes.
eg. scheduler_base create_scheduler_object(string args){
if(args == 'local') return new local();
else if(args == 'static') return new static();
}
Accordingly, this scheduler_factory will have a scheduler_factory.cpp and
scheduler_factory_base.cpp in hpx/hpx/plugins.
Is this design okay? Or did I misunderstand something?
Regards
Satyaki Upadhyay
B.E. (Hons.) Computer Science
BITS Pilani, India
ᐧ
_______________________________________________
hpx-users mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
