Hi Brian,<div><br></div><div>I don&#39;t remember the details, but what you said is completely right, when we pass an object to any of the Boost.MPI methods, it can be either of MPI type, in what case it&#39;s properly forwarded to the C implementation, or it can be of a serializable type when the magic happens.<br>
</div><div><br></div><div>At the other end of the wire, Boost.MPI will magically deserialize the object and you have no additional work. You keep working on high-level C++.</div><div><br></div><div>The main bottleneck here is the act of serialize/deserialize repeatedly. As you already know, Boost.MPI solved this problem for some cases (with fixed layout): the skeleton and content approach.</div>
<div><br></div><div>When the approach is not applicable, you have to live with C raw buffers doing the &amp;vec[0] trick. I&#39;ll take a better look to see if specializing the template with that trick is safe and covered by the C++ standard.</div>
<div><br></div><div>You&#39;re also free to investigate and produce patches. :-)</div><div><br></div><div>Regards,</div><div>Júlio.</div>