Remove Serialization from RMA

Issue #112 resolved
Dan Bonachea created an issue

In the 1/10/18 meeting, we tentatively resolved to remove the Serialization feature from RMA operations, which will always assume the type is POD and safe to perform byte-copy RDMA. This ensures rput and rget (and their VIS analogues) always use the best-available one-sided RMA mechanism for the current platform and are never doing rendezvous or multi-copy RPC for the purpose of Serialization.

I think we resolved to leave Serialization only for RPC (which is semantically two-sided by definition). However I'm not sure we considered the case of collectives, where Serialization might still fit naturally.

Serialization is currently unimplemented and only partially specified, so mostly we just need to confirm and clarify our intention to not provide it for RMA calls, and probably say something about what happens when rput/rget are called on types that are not trivially serializable.

Also note related issue #64

Comments (1)

  1. Log in to comment