Message size doesn't show correctly for Pack-Unpack

[pplimport]

Original author: Osman Sarood
Original issue: https://charm.cs.illinois.edu/redmine/issues/258

---

The message sizes only represent the 112 bytes header if pack unpack for messages is used. Parameter marshalling works correctly.
Example:

1. charm/examples/ring: Currently the example uses pack unpack methods for custom Msg type. Trace-projections fails to log the correct message size. The example currently uses a group. However, the behavior is the same for arrays.
2. If you change the same code to use parameter marshalling instead of custom message, the message size is shown correctly.

[PhilMiller]

Original date: 2013-08-28 19:08:45

---

Please do the investigation and coding necessary to fix this. Ask others for help as needed, but make sure it gets done.

[pplimport]

Original author: Ehsan Totoni
Original date: 2015-01-28 17:51:52

---

I could reproduce the case and compare with other cases. In the ring example with pack and unpack routines, the runtime doesn't have any way of knowing the message size to add to the traces. In the case of pup routines, it can call pup::size but there is no such thing here. Even the pack and unpack routines are not called when the destination is on the same processor (the pointer is passed).

When message size tracing is required, one solution is to have user events that capture it.

[PhilMiller]

Original date: 2015-01-29 18:47:05

---

If the message does cross an address-space boundary, and does get pack()ed, then the runtime can ask the envelope env->getTotalsize() after it's packed. If it doesn't cross that boundary, then the message size is literally the size of the never-packed structure.

[mprobson]

Original date: 2015-04-02 20:26:33

---

Sam, you're the default re-assignee for Ehsan's bugs so either triage this and assign it to someone else or do it yourself.