>Jean-Loup, > >> I am currently playing with HPX components in order to understand a bit >> better how they work. In particular, I am trying to migrate a component to >> a different locality from the one it was instantiated on. However, >> documentation on component migration is quite scarce and I have not been >> able to get a minimal example to work. > >What do you mean by this? What didn't work? Could you be more specific >please?
I was just trying to implement a minimal example of a migratable component (similar to the one in the gist), i.e. define a very simple class (e.g. a wrapper around some STL type), which can be copied across node boundaries. >> See the following gist to see what I am trying to achieve: >> https://gist.github.com/Element-126/c1815833fce9018fb28911751e0ce43b >> >> Looking at the HPX source code, it seems that I will need to implement >> serialization support for my component, but I have not been able to figure >> out the specifics yet. > >Yes, in order for a component to be migratable you need to make it >serializable. Otherwise there is no way to deduce what it means to move a >component over the wire (i.e. what members to 'copy', etc.). This can be >done in the usual way (see the boost serialization documentation for details >[1], the HPX serialization is very similar, except for the namespace - use >'hpx::' instead of 'boost::'). Thanks for the reference. I am not very familiar with serialization yet, so the boost documentation will certainly help a lot. >Regards Hartmut >--------------- >http://boost-spirit.com >http://stellar.cct.lsu.edu > >[1] http://www.boost.org/doc/libs/1_64_0/libs/serialization/doc/index.html Best regards, Jean-Loup
_______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
