Hartmut Kaiser
Hartmut Kaiser
> Yes, this is expected behavior. Not sure if we can do anything about this, I'll have a look. To explain, the macro argument is used in places where a...
If this will not be fixed for V1.4, please add a 'known problems' to the release notes.
We know that parts of the macros can be avoided at the expense of increasing compile time (possibly significantly). It might also be possible to use some of the new...
Is there anything we have to do in HPX? This seems to be something that has to be changed in Blaze.
How did you determine the size of the `transfer_action`? From what I can see the `transfer_action`'s size is determined mostly by the sizes of the arguments passed to the remote...
> I looked at the archive size before serializing the action and after. Ahh. I think this particular action might even have a configuration defined size as it transfers the...
@biddisco I assume this can be closed now, can it?
Looks like a missing #include somewhere. I'll try to investigate...
Instead of adding new special arguments to `async`, wouldn't it be possible to have something like: ``` async(policy, an_rdma_action_type(rdma_object_id), locality, ...) ``` or ``` async(policy, an_rdma_action_type(), rdma_destination(locality, rdma_object_id), ...) ```...
The second one is less desirable, though, as it splits the notion of sending something through the RDMA extensions and requires the user to specify it through two of the...