Hi Jean Look at migrate components in the docs section. I hope that will solve your issue : )
*https://stellar-group.github.io/hpx/docs/html/hpx.html#hpx.components.migrate_idm139960999697024 <https://stellar-group.github.io/hpx/docs/html/hpx.html#hpx.components.migrate_idm139960999697024>* On 18 July 2017 at 21:07, <[email protected]> wrote: > Send hpx-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.cct.lsu.edu/mailman/listinfo/hpx-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of hpx-users digest..." > > > Today's Topics: > > 1. Minimal example of component migration (Jean-Loup Tastet) > 2. Re: Minimal example of component migration (Hartmut Kaiser) > 3. Minimal example of component migration (Jean-Loup Tastet) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 18 Jul 2017 13:41:46 +0000 > From: Jean-Loup Tastet <[email protected]> > Subject: [hpx-users] Minimal example of component migration > To: "[email protected]" <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > 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. > > 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. > > Could anyone point me in the right direction ? > > Thanks ! > Jean-Loup > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://mail.cct.lsu.edu/pipermail/hpx-users/ > attachments/20170718/a12c21f9/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Tue, 18 Jul 2017 09:29:45 -0500 > From: "Hartmut Kaiser" <[email protected]> > Subject: Re: [hpx-users] Minimal example of component migration > To: <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > 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? > > > 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::'). > > 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 > > > > > > ------------------------------ > > Message: 3 > Date: Tue, 18 Jul 2017 15:08:24 +0000 > From: Jean-Loup Tastet <[email protected]> > Subject: [hpx-users] Minimal example of component migration > To: "[email protected]" <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > >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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://mail.cct.lsu.edu/pipermail/hpx-users/ > attachments/20170718/d795fda1/attachment.html > > ------------------------------ > > _______________________________________________ > hpx-users mailing list > [email protected] > https://mail.cct.lsu.edu/mailman/listinfo/hpx-users > > > End of hpx-users Digest, Vol 50, Issue 5 > **************************************** >
_______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
