> I have gone through the list of possible projects for GSOC 2016 and two > have really caught my fancy. > > > Implement a plugin mechanism for thread scheduling > Via discussions on IRC, I have come to understand that this entails > detangling the 6 schedulers from HPX and create separate shared libraries > to be loaded at runtime. I have read the docs regarding the thread > scheduling policies and executors in HPX. Could someone give me some > pointers as to how I should move forward with this? Any resources or > material to read up to get some more idea about this? Any help would be > appreciated.
Andy has already responded wrt the other project you mentioned, I'll refer to the thread scheduler plugin mechanism only. The point of this project is to convert the currently statically linked thread schedulers in HPX into separate modules which can be loaded at runtime as needed. Some of this work has already be done in the code, but most of the required refactoring is still to be done. This is a nice GSoC project as it is not too hard, does not require too intimate knowledge of HPX, but at the same time, might have a big impact on HPX's usability. You might want to start with checking out HPX, building it, making the examples run. You might want to dig into what HPX actually is (read the docs and publications) to get an idea what we try to achieve. Once you have a better understanding you should start to look into HPX itself to understand the current structure and to understand how schedulers are built into it today. Please stay in close contact either via this mailing list or through the IRC channel while you start writing your proposal which you'll have to submit at the end of this month. HTH Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
